Skip to content

[1.0] Move filtering on graphql connections under top-level "filter" key #1174

@KyleAMathews

Description

@KyleAMathews

Should have done this awhile ago but just occurred to me earlier when I was explaining filtering on connections w/ GraphQL that it'd be much easier to understand if all fields you could filter on were under a "filter" key. That way the only top-level keys/fields would be skip, limit, sort, and filter. Much more straightforward to understand.

Also, sortBy should just be sort.

Also add connection fields before node fields as that's generally what you want to query in graphiql.

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