-
Notifications
You must be signed in to change notification settings - Fork 310
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
QuerydslDataFetcher.buildPredicate(…)
does not unwrap nested argument maps into fully-qualified property paths
#1081
Comments
If you would like us to spend some time helping you to diagnose the problem, please spend some time describing it and, ideally, providing a minimal yet complete sample that reproduces the problem. |
This is my example repository: https://github.com/zeng-alt/graphql-test This is my solution, but it's not very good:https://github.com/zeng-alt/zero-ddd/tree/master/zero-ddd-component/zero-ddd-graphql-component |
This is indeed a bug on our side. We're storing incoming arguments in a map expecting keys of the map to represent full property paths. In this case ( What should happen is that we unwrap all nested maps and form an argument map with fully-qualified keys ( Stack trace:
|
QuerydslDataFetcher.buildPredicate(…)
does not unwrap nested argument maps into fully-qualified property paths
There is a problem with the QuerydsDataFetcher join query. Can I modify the QuerydsDataFetcher.getArgumentValues method to fix it?
/**
* For a single argument that is a GraphQL input type, return the sub-map
* under the argument name, or otherwise the top-level argument map.
*/
@SuppressWarnings("unchecked")
private static Map<String, Object> getArgumentValues(DataFetchingEnvironment environment) {
The text was updated successfully, but these errors were encountered: