Skip to content

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

@mieubrisse

Description

@mieubrisse

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"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions