Skip to content

[name]ModelSelector requires passing 'undefined' instead of empty for non-primitive fields #407

Description

@wtuminski

I tried to upgrade mst-gql in my project, but when I did so it turned out that I must pass undefined to every empty selector builder of a non-primitive field. In many queries, I want to get only a reference so when invoking the selector builder for a non-primitive field I pass no arguments. The builder argument is now required, but undefined is acceptable. Can't we return to the optional argument?

Activity

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

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