Array, Set, or Page expected, Object provided on @resolver

[ptpaterson]

I created a separate post to detail the bug that I think is at fault.

Updating GraphQL Schema bug when changing from Named, List, or NonNull

Trying to puzzle out a recent post from @jorfermo I’ve found that uploading a schema that changes the output type of a custom resolver does not work correctly. It appears to actually append the newer type, which then just gets ignored whenever the meta data is transformed into a schema. Simplest case: this is an entire schema definition to upload. Start with a function that outputs a Named type. type Query { hello: String @resolver } try to change it to a List type type Query { hello…

You can confirm by checking the meta data

Get(Function('verify_user'))