-
Notifications
You must be signed in to change notification settings - Fork 182
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
Functions schema validation failure in v11.0.0 #375
Comments
This issue has been copied into our private issue tracker (as PDE-2410). Thanks for the report! We'll update this as we learn more. |
Great find! I'll get that shored up. In the meantime, you can downgrade |
The fix is merged and it'll go out in the next release sometime in the next few weeks. Thanks for the report! |
Great! Thanks for the super quick turnaround 🤘🏼 |
@EtienneLem this is released with |
Awesome, thanks! |
Bug Description
Trying to upgrade to v11.0.0, we’re now getting schema validation errors.
Here’s an example of the error messages we’re getting:
Looking at the schema docs and the validation implementation of #347, it feels like it might not be handling the cases of functions? Validation takes for granted that
key
is required, but if my understanding of the schema is correct,FunctionSchema
does not require akey
.Reproduction Steps
These key-less fields are functions. Both async and sync fails the validation. Our
inputFields
are typically structured like this:Here it would probably fail when validating
getDynamicField
because "undefined" is already in use atinputFields[2]
.Version Info
The text was updated successfully, but these errors were encountered: