graphql

timgilbert 2019-03-12T15:11:00.031300Z

Say, I'm seeing some contradictory advice in the lacinia docs. Here it says: > The parse and serialize callback functions should not throw an exception; instead, to indicate a parsing or serializing problem, they may return nil, or create a coercion failure result by invoking the function com.walmartlabs.lacinia.schema/coercion-failure. https://lacinia.readthedocs.io/en/latest/custom-scalars.html#handling-invalid-values ...but in the API docs it says: > This is deprecated in version 0.32.0; just throw an exception instead. http://walmartlabs.github.io/apidocs/lacinia/com.walmartlabs.lacinia.schema.html#var-coercion-failure

timgilbert 2019-03-12T15:11:41.031700Z

Which is more up to date?

orestis 2019-03-12T17:40:26.032400Z

I believe API docs.