You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
.The text was updated successfully, but these errors were encountered: