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

Update api/v1/person endpoint to not use camel-case personType query parameter #9389

Closed
jkuester opened this issue Aug 28, 2024 · 0 comments · Fixed by #9390
Closed

Update api/v1/person endpoint to not use camel-case personType query parameter #9389

jkuester opened this issue Aug 28, 2024 · 0 comments · Fixed by #9390
Assignees
Labels
Type: Improvement Make something better
Milestone

Comments

@jkuester
Copy link
Contributor

We do not have a ton of consistent conventions for our REST api, but one that we do have is that all our current query parameter names are snake-case and not camel-case.

For the recently added (and as of yet unreleased) support for getting persons by type, I missed in the code review that the query parameter was named personType.

We should just change this to be type since semantically the "person" part is redundant: api/v1/person?type=my-person-type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Improvement Make something better
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant