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

Collections in query params are being deprecated and collections in path are forbidden #593

Open
mieubrisse opened this issue Apr 26, 2020 · 0 comments

Comments

@mieubrisse
Copy link

mieubrisse commented Apr 26, 2020

What happened?

Using a collection as a query param results in "Collections as query parameters are deprecated and will be removed in a future release", and using a collection in a path is forbidden: "Path parameters must be primitives or aliases"

What did you want to happen?

The generally accepted way to retrieve multiple resources in a single HTTP request seems to be including it in the URL, either as a way query param or part of the path (1, 2, 3 ). Forcing queries retrieving multiple resources to be in POST would deviate a bit from the general "GET for retrieving resources, POST for creating/retrieving resources"

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

No branches or pull requests

1 participant