Skip to content

Refactor info record structure #4

Description

@datadavev

The info response is a bit organic and should be refactored a little to reflect the different aspects of the response. Perhaps something like:

{
  "parsed": {
  // Info from the results of parsing the input
  },
  "computed: {
  // Results of computing target, redirect code, canonical form
  },
  "metadata": {
    // Info from the matching PID definition
  },
}

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions