-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Argument deserialization #56
Comments
Currently, args do not undergo any name transformation like properties do. There's not a particular reason for this, and I'm open to changing it. We do support input objects (https://facebook.github.io/graphql/#sec-Input-Values), but we may not handle optional fields very well. Deserializing an input object with arbitrary fields (say to a |
Do you have any plans for working on a feature like this? |
I think adding deserialization to a Dictionary is a sensible thing to do. We've considered how to handle optional fields when deserializing to an object and it's a bit tricky, since I think we would need to introduce our own attributes and reflect over them (e.g. how to handle non-nullable reference types). Also, I'm happy to accept any PRs that add features within the scope of the project. |
I'm playing with graphql-net and I really like it.
One thing that I can't figure out is how args are deserialized.
It seems that camelCase/pascalCase conversion is not working for args.
Also, is it possible to get a plain JSON object (patch)?
A patch would be very useful as it includes information which fields should be updated. That's not available with strongly typed models.
The text was updated successfully, but these errors were encountered: