Feature request: Custom deserialization of scalars/object types/interface types

[helios1138]

Feature request: Custom deserialization of scalars/object types/interface types

[helios1138]

@capaj custom scalar type mapping implemented in v1.2.0. Object mapping is more tricky and probably lies outside of the scope of this project.

[capaj]

another thought-it would be nice to be able to turn it off/override per query. There might be cases when you query data you might not want to deserialize.
So ideally I could pass the same hashmap as another argument to query/mutation/subscription. If I pass a falsy value it should just give me raw JSON values even if I have top level deserialization map.

[helios1138]

would be nice to be able to turn it off/override per query

@capaj can you describe the case where you would want both deserialized and original values (or same types deserialized differently) in the same application?

Rendering custom types based on some deserialization mapping provided during client generation seems easy enough, but I don't see an easy way to do it dynamically during execution