Resolver wrapper should not check for sequential for custom scalar types about lacinia HOT 4 CLOSED

We'll need to look into using type information to figure out whether to map the results or just use the single result. Should not be impossible.

from lacinia.

So you are returning a value, but it looks like an array to Lacinia, but you have a scalar for the value type such that it can be serialized into the response as is. Right?

This is, to me, an odd edge case.

Could you wrap your JSON value in a wrapper that isn't a sequential, and have your :serializer extract the nested value?

from lacinia.

That is correct, I had a scalar JSON type that I was using which was sometimes an array. I wound up wrapping it like you suggested as a work-around. I was just surprised by the error.

It might help to have an example of this in the documentation to clarify when the :serializer functions are run.

from lacinia.

I think this is a wont/cant fix.

from lacinia.