-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
Rules don't work an array of a custom type input #930
Comments
Can you create a PR with a test showing the (unexpected) behavior? The idea being that the test is green but based on the current behavior to have a point of reference. |
Sure, I can do it in a few hours 😄 |
Appreciated, will take a look after I'm back from vacation |
Thank you, hope you enjoy your vacation. I've just left to mine, otherwise I could take a better look at this 😅 |
yeah, right now this only works if you do: prohibits:recipients.mintParams so it is dependent on the whole path which is not ideal |
Maybe this is something for a known limitation section, with an example how to work with this? |
Versions:
Description:
Rules don't work properly when they are in a type inside of a list.
I have a mutation called
BatchMint
with the following args:MintRecipient
has the following fields:The rules on the address field work fine. But the prohibits, required_unless, required_without, or any rule that makes a reference to another field don't work. I know those rules work fine when they are in the arguments but they don't work when they are in the array of types.
The text was updated successfully, but these errors were encountered: