Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request] Add ability to generate union type resolver based on __typename field
See original GitHub issueIs your feature request related to a problem? Please describe. When using union type with graphql-java-codegen, we need to define a way to tell Jackson how to choose which implementation depending on the data. This step could be generated.
Describe the solution you’d like
The spec (https://graphql.org/learn/schema/#union-types) defines the __typename field which will be populated with the data type.
It would be possible to generate Jackson annotations & resolver based on the __typename field.
This behaviour could be linked to a configuration toggle, and could be overwritten by customAnnotationsMapping configuration.
Describe alternatives you’ve considered Stay with current implementation.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In the case a modelPackageName is empty, I see that it defaults to packageName. And if both modelPackageName & packageName, the class will be generated in the default root package.
Ok for the proposed switch name and default value.
I will send a PR soon.
I will give it a try.