[Schemas] Define all fields in ui:order to prevent crash #374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes #
Recently we get
*
wild card issues in Meshery from RJSF form and error wasYou can't use multiple wild cards in ui:order
even if we were using the single wild card and removing it fixes the issue in Meshery and works fineAs a result, it crashes in Meshery cloud RJSF forms and the form and error is
include all field in ui:order
I think this was because of different RJSF versions in both applications, though to prevent that in the future we will make sure to not use*
wild card and explicitly define all fields in ui:orderFYI wild card helps us not to explicitly define ui order for all fields in form all the time, with the help of wild card we can define the order of some fields and the rest can render after that
Notes for Reviewers
Signed commits