You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #925 includes a change to start validating the default value of input fields and arguments. This turns out to break enough existing schemas (Router rejects them as invalid where it previously accepted them) that we consider it a breaking change. After some discussion, our plan is:
Revert default value validation for now
Publish a new compiler beta without it to unblock current work
Finish up compiler 1.0 stable and use it in Router before its 1.x LTS
Stricter validation, which we consider a breaking change, will be in compiler 2.0which will be used by router 2.0. This is the part tracked by this issue
If needed later, we can backport LTS fixes to compiler 1.x
The text was updated successfully, but these errors were encountered:
For reference, graphql-js only recently started validating default input values in graphql/graphql-js#3814. Version 16.x used by router-bridge does not.
This turns out to break enough existing schemas
(Router rejects them as invalid where it previously accepted them)
that we consider it a breaking change.
See #928
This turns out to break enough existing schemas
(Router rejects them as invalid where it previously accepted them)
that we consider it a breaking change.
See #928
PR #925 includes a change to start validating the default value of input fields and arguments. This turns out to break enough existing schemas (Router rejects them as invalid where it previously accepted them) that we consider it a breaking change. After some discussion, our plan is:
The text was updated successfully, but these errors were encountered: