feat: add ui:definitions for recursive and reusable uiSchema #4947
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.
Reasons for making this change
This PR adds a new
ui:definitionsproperty to uiSchema, enabling UI customizations for schema$refreferences. This addresses a long-standing limitation where there was no way to define uiSchema for recursive schemas or to avoid repeating uiSchema for reused definitions.Relates to #670 (Recursive references and uiSchema) and #477 (uiSchema for definitions)
The Problem:
The Solution:
Key features:
oneOf/anyOfbranches$refpaths (e.g.,#/definitions/addressor#/$defs/node)Changes:
expandUiSchemaDefinitions()andresolveUiSchema()functions,UiSchemaDefinitionstype, and related constantsSchemaFieldui:definitionsChecklist
npx nx run-many --target=build --exclude=@rjsf/docs && npm run test:updateto update snapshots, if needed.