Implement onError proposal (but with ErrorBehavior rather than __ErrorBehavior)#4384
Implement onError proposal (but with ErrorBehavior rather than __ErrorBehavior)#4384
ErrorBehavior rather than __ErrorBehavior)#4384Conversation
|
Hi @benjie, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
This comment has been minimized.
This comment has been minimized.
@benjie The latest changes of this PR are available on NPM as Also you can depend on latest version built from this PR: |
|
@github-actions publish-pr-on-npm |
| { name: 'Droid' }, | ||
| { name: 'Query' }, | ||
| { name: 'Boolean' }, | ||
| { name: 'ErrorBehavior' }, |
There was a problem hiding this comment.
I am unsure whether we should expose this as a schema property, this is in fact an internal property that tells us just how a GraphQL API will behave. Most GraphQL code I've seen treats it as such where when walking the introspection there is an explicit check for properties starting with __ to be skipped.
|
Closing in favour of #4364 to keep things tidier. That will also need updating. |
2 participants
Alternative to:
Using
__ErrorBehaviorcauses older GraphiQL to baulk. I'm hoping that this approach will not.