Skip to content

JsonApiListener does not respect "include" query parameter if "fields" query parameter is used. #174

@geoidesic

Description

@geoidesic

E.g.

{{protocol}}{{domain}}/api/people/3c9b642a-6682-4b7a-aff2-1928371923719?fields[people]=role&include=role

This will not include any data and currently produces the same result as this query:

{{protocol}}{{domain}}/api/people/3c9b642a-6682-4b7a-aff2-1928371923719?fields[people]=role

Which means that there is no way currently to fetch a single entity and only receive some of its related data, which means GET entity requests will be exponentially slower – a ticking time-bomb in your app. Nice. Hard to believe no-one noticed this before.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions