Custom scalar isn't being respected about apollo-ios HOT 7 CLOSED

Yea. In this case it's true but it could be for example 54. I've defined init(_jsonValue value: JSONValue) so I'm not sure why it's being decoded as a plain Bool for this response.

from apollo-ios.

That was it, thanks! I was waiting to trim code until things started working 🤦

Appreciate your help!

from apollo-ios.

Hi @solidcell - is the data value being sent as regular JSON bool? Something like this:

{
  result: true
}

from apollo-ios.

Are you able to share the definition for BasicScalar? Does the behaviour change if the value is 54 for example, i.e.: something other than a boolean value?

from apollo-ios.

https://www.loom.com/share/b8b4ae318a94464a96b63f1ddb47bc48?sid=e9c3f788-be91-469d-8e41-be67a06850a9

from apollo-ios.

OK, I think the issue is your implementation of _asAnyHashable. It in turn calls the private function hashable which is returning the base type such as Bool or Int. I believe it's that value that ends up getting stored in DataDict. You shouldn't need to define _asAnyHashable at all. Essentially you're turning your custom scalar back into the base type.

Here is a sample project which defines a custom scalar pretty similar to yours just with less variants to it. The test passes with the custom scalar type being returned as expected. In the custom scalar file there is a commented out portion with the same _asAnyHashable and hashable functions that you have, and if you uncomment that section you'll get failures in the test with the same error you're seeing.

tl;dr - remove your _asAnyHashable function and it should work as expected.

from apollo-ios.

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better.

from apollo-ios.