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

Principle #6 – Put Complexity behind the ‘?’ #8

Closed
cmheazel opened this issue Jul 10, 2018 · 2 comments
Closed

Principle #6 – Put Complexity behind the ‘?’ #8

cmheazel opened this issue Jul 10, 2018 · 2 comments

Comments

@cmheazel
Copy link
Collaborator

• This where the fun begins
• query-string parameters should be used to select a resource(s) based on the(ir) characteristics
– /v1/features/highways?id=A8 => returns highway A8
– /v1/features/highways?id=A8,A9 => returns highways A8 and A9
• But what if you select on a resource instance?
– /v1/features/highways/A8?id=A8
should that return true or the resource?
– /v1/features/highways/A8?id=A81
should that return false or null?
• Use of the query string to select resources is highly domain specific and must be described on a case to case basis

@cportele
Copy link
Member

I do not understand what this principle is trying to say. How can the path "be identical regardless of the kind of resource"? What is meant by "domain specific aspects"? Etc. I suggest to remove this principle. Or rewrite to clarify what is meant.

@securedimensions
Copy link
Collaborator

now addressed in master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants