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
So when the sequence is longer and thus Clojure internally handles it as a ChunkedSeq instead of an IndexedSeq, the collection in the arguments is processed to become a list with keywords, instead of a vector with symbols. In the ChunkedSeq case the query generated is invalid GraphQL.
Workaround
Ensure the sequence passed to graphql-query is not of type ChunkedSeq, for example by marshalling the sequence into a vector.
The text was updated successfully, but these errors were encountered:
When passing a sequence to the
graphql-query
function this leads to different behaviour whether the sequence is aChunkedSeq
or anIndexedSeq
.Example
So when the sequence is longer and thus Clojure internally handles it as a
ChunkedSeq
instead of anIndexedSeq
, the collection in the arguments is processed to become a list with keywords, instead of a vector with symbols. In theChunkedSeq
case the query generated is invalid GraphQL.Workaround
Ensure the sequence passed to
graphql-query
is not of typeChunkedSeq
, for example by marshalling the sequence into a vector.The text was updated successfully, but these errors were encountered: