docs: remove reference to the deprecated uiSchema classNames property
#3294
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
In the v5 migration guide, it is explained that `classNames` property within uiSchema is now deprecated in favor of `ui:classNames` property. In developer use the legacy classNames, a deprecation warning is displayed within the console . But currently, in the uiSchema section within the quickstart guide, documentation still refer to this deprecated property that is weird for newcomers which will bootstrap a project with deprecation warnings.
heath-freenome
approved these changes
Dec 19, 2022
shijistar
pushed a commit
to shijistar/react-jsonschema-form
that referenced
this pull request
Jun 8, 2023
…ty (rjsf-team#3294) In the v5 migration guide, it is explained that `classNames` property within uiSchema is now deprecated in favor of `ui:classNames` property. In developer use the legacy classNames, a deprecation warning is displayed within the console . But currently, in the uiSchema section within the quickstart guide, documentation still refer to this deprecated property that is weird for newcomers which will bootstrap a project with deprecation warnings. Co-authored-by: Heath C <51679588+heath-freenome@users.noreply.github.com>
shijistar
pushed a commit
to shijistar/react-jsonschema-form
that referenced
this pull request
Jun 8, 2023
…ty (rjsf-team#3294) In the v5 migration guide, it is explained that `classNames` property within uiSchema is now deprecated in favor of `ui:classNames` property. In developer use the legacy classNames, a deprecation warning is displayed within the console . But currently, in the uiSchema section within the quickstart guide, documentation still refer to this deprecated property that is weird for newcomers which will bootstrap a project with deprecation warnings. Co-authored-by: Heath C <51679588+heath-freenome@users.noreply.github.com>
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.
Reasons for making this change
In the v5 migration guide, it is explained that
classNamesproperty within uiSchema is now deprecated in favor ofui:classNamesproperty. When developer uses the legacy classNames, a deprecation warning is displayed within the console . But currently, in the uiSchema section within the quickstart guide, documentation still refers to this deprecated property that is weird for newcomers which will bootstrap a project with deprecation warnings.Checklist