Fix tabs render order in nested schema with ui-schema #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix handling of recursive uiSchema structure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When we create a nested schema that employs a widget multiple times (not needed to give the same one multiple times) and provide a UI order for the inner schema, the tabs become disrupted. They revert to using the default JSON order, and during rendering, the tabs may be pushed down to the second or third row, depending on the first key. You can see a live preview of this issue in action by visiting this link:
https://codesandbox.io/s/rsjf-widget-with-body-9gh2x6?file=/src/App.js