-
Notifications
You must be signed in to change notification settings - Fork 226
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
Automatic object derivation for complex types #231
Comments
The You will also need to define/import an implicit instance of |
Thank you, Now another question :) How about maps? I know they don't make much sense in this context but if we were to implement an @OlegIlyenko Thank you so much for your help - sangria (and especially the macros) has been great! |
Thank you for your kind words! 🙇 Using a raw JSON scalar can be an option, but I would discourage using it, especially considering that you have simple |
Sorry for the long delay but been on holidays. That link provided some useful clues on how to solve this, so thanks :) |
Just ran into this. Might be nice to mention somewhere in the README a list of gotchas like this to save people some time. |
Hi,
If I have a case class with complex types, e.g..
and then do automatic object derivation
then these kinds of errors appear:
Once we have GraphQL types for the base types, in this case, String and IndexComponent, can't Sangria automatically derive List's and Set's of them?
I can define a GraphQL output type for Set[String] but it doesn't make much sense.. so I think I'm probably missing something.
So how does one provide an output type in these kinds of cases?
Thanks!
The text was updated successfully, but these errors were encountered: