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.

Sign up for GitHub

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

Jump to bottom

Align API spec format with the latest Commonalities agreements #33

Closed
jpengar opened this issue Mar 21, 2023 · 2 comments
Closed

Align API spec format with the latest Commonalities agreements #33

jpengar opened this issue Mar 21, 2023 · 2 comments
Assignees
@jpengar

Comments

@jpengar
Copy link
Collaborator

jpengar commented Mar 21, 2023 •
edited
Loading

Align API spec format with the latest Commonalities agreements:

  • Commonalities - adjust the error status field, which will eventually be an integer (not a patterned string): PR #145.
  • Commonalities - adjust the schema references in the errors responses and apply the agreed solution: Issue #151 & PR #162.
  • Commonalities - change the format of the API fields to lowerCamelCase: Issue #157, Discussion #169 & PR #171.
@jpengar jpengar self-assigned this Mar 21, 2023
@jpengar jpengar changed the title Align API spec format with the latest Commonalities agreements. Align API spec format with the latest Commonalities agreements Mar 21, 2023
@jpengar jpengar mentioned this issue Mar 21, 2023
Merged
@jpengar
Copy link
Collaborator Author

jpengar commented Mar 21, 2023

Addressed at #34

@monamok
Copy link
Collaborator

monamok commented Mar 31, 2023

PR#34 was approved and merged.

@monamok monamok closed this as completed Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpengar jpengar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpengar @monamok