-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
keyArgs: array of objects support #11198
Comments
In such a complex case, you can use a We aim to provide functionality for all the common use cases, but once it gets complex like this, it's impossible for us to find a notation that fits everyone - and if we could find one, it would add significant bundle size as a burden to everyone, including those who would not be needing it. In that case, it's better (and probably much simpler to use for you) to implement this in userland.
PS2: Please excuse the back-and-forth - I stand with my initial answer. We do have a feature like that, but only for objects, not arrays. In the array case, please provide your own function. |
@phryneas thanks for your feedback. I will provide then a working example here so it can be used as reference for people having the same usecase. PS: I noticed that the |
@younes0 The |
@phryneas my bad, i was wrong. |
specifying I will change my GraphQL schema in the end to avoid nested object in arrays. |
I changed my GraphQL schema to accept a (JSON) string value. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
There is not support array of objects as
keyArgs
.With variables
The following field policies do not work
This question/feature was already asked but didn't get any answer: #7314 (comment)
The text was updated successfully, but these errors were encountered: