Chore remove unnecessary formContext from all interfaces but Registry #4743
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
Since the
registry
containsformContext
and it is part of all interfaces that hadformContext
, removedformContext
@rjsf/utils
, removedformContext
from the following interfaces:ErrorListProps
,FieldProps
,FieldTemplateProps
,ArrayFieldTemplateProps
andWidgetProps
@rjsf/core
, updatedArrayField
,Form
,LayoutMultiSchemaField
andSchemaField
to stop passingformContext
formContext
from theregistry
@rjsf/antd
, updated theArrayFieldTemplate
,FieldTemplate
andObjectFieldTemplate
to getformContext
from theregistry
@rjsf/daisyui
, removedformContext
usages@rjsf/primereact
, updated the snapshots to removeformContext
formContext
from the interface documentation, adding a BREAKING CHANGE notification in thev6.x upgrade guide
@rjsf/semantic-ui
, updated the use offormContext
to get it fromregistry
CHANGELOG.md
accordinglyChecklist
npx nx run-many --target=build --exclude=@rjsf/docs && npm run test:update
to update snapshots, if needed.