Type system is insufficient - list and not-null can not be freely combined about lacinia

[mpenet]

👍

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.

[bcarrell]

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> .

[kgann]

@mpenet

If you're willing to change your schema, I think you could use wrapper objects as a workaround. I haven't tested this.

:input-objects
{:inputInts {:fields {:ints {:type (list Int)}}}}

:objects
{:ints {:fields {:ints {:type (list Int)}}}}

:queries
{:foo {:args {:ints {:type (list :inputInts)}}}
       :type (list :ints)
       :resolve :foo-resolver}

Arguments and resolved types may be a bit odd:

{
  foo(ints: [{ints: [1, 2, 3]}, {ints: [4, 5, 6]}]) {
    ints
  }
}

{:data {:foo [{:ints [1 2 3]}
              {:ints [4 5 6]}]}