Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation API should be public, and accept either a schema name or an organization.sender name. #7927

Closed
jimduff-usds opened this issue Jan 11, 2023 · 0 comments · Fixed by #8056
Assignees
Labels
platform Platform Team

Comments

@jimduff-usds
Copy link
Member

jimduff-usds commented Jan 11, 2023

The public facing validator page will support validation against a few known/popular schema names, that will initially be hardcoded.

Because it is public, the UI does not know an organization name nor sender name to use. So it must submit data for validation using the schema name.

Acceptance Criteria

  • This ticket is to change the validation API to accept a header with the schema name OR a header with an organization.sender name.
  • Unit tests written
  • Make the API public
  • Confirm you didn't break the old organization.sender functionality.
  • Confirm with Stephen N.
  • Confirm its ok with the Xperiencites
  • Update (or create?) the appropriate documentation in docs/api/

Discussion

  • Should we allow schema-name based submissions for the "real" submission endpoints too?
  • Current header for sender name is of the form client: organization.sender
  • New form can be schema: path/schema-name
  • Note that each schema knows its "topic"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Platform Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants