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
The current system is quite limited: you can add a not-null qualifier, meaning that the value may not be nil. You can add a list qualifier, meaning that the resolver returns a seq of values, not a single one. You can combine the two, meaning that the the values may not be nil (though the list itself may be).
This is a subset of what the GraphQL spec calls for; we should be able to say that a field's type is a non-null list of lists of non-null Strings, for example.
That means the list and not-null qualifiers need to be fully nestable, with some system of reified types to make it all work; a somewhat fundamental change to how the executor operates.
The text was updated successfully, but these errors were encountered:
I am actually in need of (list (list Int)) to port our schemas to graphql, I am not sure how to model this in the meantime. If you have workarounds feel free to advise me.
Right. This is something that we've known was an issue for a while but we
don't have that issue with our services. Let's prioritize this to be fixed
asap.
On Mar 28, 2017 4:25 AM, "Max Penet" ***@***.***> wrote:
👍
I am actually in need of (list (list Int)) to port our schemas to
graphql, I am not sure how to model this in the meantime. If you have work
arounds feel free to advise me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA99BEfXqC_rpCX4kl-5-Sd_2THYBO2vks5rqMQTgaJpZM4Mq3J1>
.
The current system is quite limited: you can add a not-null qualifier, meaning that the value may not be nil. You can add a list qualifier, meaning that the resolver returns a seq of values, not a single one. You can combine the two, meaning that the the values may not be nil (though the list itself may be).
This is a subset of what the GraphQL spec calls for; we should be able to say that a field's type is a non-null list of lists of non-null Strings, for example.
That means the
list
andnot-null
qualifiers need to be fully nestable, with some system of reified types to make it all work; a somewhat fundamental change to how the executor operates.The text was updated successfully, but these errors were encountered: