This repository was archived by the owner on Apr 14, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Multi-head connections does not support nullability #200
Labels
bug
Something isn't working
Comments
I want to clarify a bit why I think Now we determine 'orphan connection' inside a resolve function of a certain connection variant. But it is possible to determine it before choosing a variant in case when determinant fields are the same for all connection vairants. |
SudoBobo
added a commit
that referenced
this issue
Aug 2, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 2, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 2, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 2, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 6, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 7, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 8, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 8, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 8, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 9, 2018
SudoBobo
added a commit
that referenced
this issue
Aug 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Consider the schema:
And collections:
We can have a
hero
object like:The above query is expected to work, but it does not:
Executing produces an error:
The text was updated successfully, but these errors were encountered: