@rjsf/core
Advanced tools
Changelog
v5.0.0-beta.1
@rjsf/utils
library functions and typestemplates
as part of the fix for https://github.com/rjsf-team/react-jsonschema-form/issues/2526
BaseInputTemplate
should fix (https://github.com/rjsf-team/react-jsonschema-form/issues/2926, https://github.com/rjsf-team/react-jsonschema-form/issues/2889, https://github.com/rjsf-team/react-jsonschema-form/issues/2875, https://github.com/rjsf-team/react-jsonschema-form/issues/2223)title
and description
consistent across themes, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2481, https://github.com/rjsf-team/react-jsonschema-form/issues/2363, https://github.com/rjsf-team/react-jsonschema-form/issues/2219)package.json
and package-lock.json
files to be built and maintained by Node 16.utils.js
file from core
into independent functions.
types
from core
in utils
to better match the implementation across all themes
formData
change when liveOmit=true
when "additionalProperties: false" issue 1507 (https://github.com/rjsf-team/react-jsonschema-form/pull/2631)validator.js
file from core
into independent functions as well as a class that implements the new ValidatorType
interface.
ajv
instance.toErrorList()
was made so that it takes fieldPath: string[]
rather than fieldName='root'
as part of the fix to (https://github.com/rjsf-team/react-jsonschema-form/issues/1596)
errors
also now adds property
from the fieldPath
along with the proper path from the property
to the stack
message, making it consistent with the AJV errors.
stack
attribute would say root: error message
; now it says . error message
errors
when merged with custom validation, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/1596).ui:emptyValue
now works with selects (https://github.com/rjsf-team/react-jsonschema-form/issues/1041)utils.js
into the new @rjsf/utils
fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/2719)ui:field
with anyOf or oneOf no longer rendered twice (#2890)anyOf
and oneOf
getting incorrect, potentially duplicate ids when combined with array (https://github.com/rjsf-team/react-jsonschema-form/issues/2197)formContext
is now passed properly to SchemaField
, fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/2394, https://github.com/rjsf-team/react-jsonschema-form/issues/2274)ui:duplicateKeySuffixSeparator
to customize how duplicate object keys are renamed when using additionalProperties
.extraErrors
are now consistently appended onto the end of the schema validation-based errors
information that is returned via the onErrors()
callback when submit fails.
errors
during the merge process, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/1596).RadioWidget
to no longer use random numbers fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2461)onChange
handler in the new set of props if it changed, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/1708).onChange
when formData
is controlled prop, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/513),@rollup/plugin-replace
to replace antd/lib
and rc-picker/lib
with antd/es
and rc-picker/es
respectively, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2962)withTheme
customizations should work properly now (https://github.com/rjsf-team/react-jsonschema-form/issues/2058)ArrayFieldTemplate
refactor seems to have fixed https://github.com/rjsf-team/react-jsonschema-form/issues/2775SelectField
(https://github.com/rjsf-team/react-jsonschema-form/issues/2616, https://github.com/rjsf-team/react-jsonschema-form/issues/2875)@rjsf/mui
) was split out of the theme for version 4 (i.e. @rjsf/material-ui
) to resolve the following issues:
inputType
in uiSchema (https://github.com/rjsf-team/react-jsonschema-form/issues/2057)
step
for number
type (https://github.com/rjsf-team/react-jsonschema-form/issues/2488)@rjsf/mui
) was split out of the theme for version 4 (i.e. @rjsf/material-ui
) to resolve the following issues:
inputType
in uiSchema (https://github.com/rjsf-team/react-jsonschema-form/issues/2057)
step
for number
type (https://github.com/rjsf-team/react-jsonschema-form/issues/2488)main
definition in semantic-ui
to fix (https://github.com/withastro/astro/issues/4357)ui:field
with anyOf
(#2890)Changelog
4.2.1
Changelog
4.2.0
ui:orderable
and ui:removable
in arrays (#2797)material-ui
context and hook (#2757)@rjsf/material-ui/v4
and @rjsf/material-ui/v5
sub-package
@rjsf/material-ui
was retained to avoid a breaking change, but using it will continue to cause bundler warningsREADME.md
for the @rjsf/material-ui
package for updated usage informationmaterial-ui
by removing the DefaultChildren
passed into the themesChangelog
v4.1.1
useMuiComponent()
hook as a shortcut for useContext(MuiComponentContext)
Changelog
v4.1.0
toIdSchema()
typescript definition to add new idSeparator
prop along with the spelling of idPrefix
idSeparator
prop through to the AnyOfField
and OneOfField
inside of SchemaField
ArrayField
in @rjsf/core
to pass idSeparator
and idPrefix
through to SchemaField
, fixing a small bugui:hideError
feature, which allows you to hide errors at a field levelconsole.log()
of the import error in MaterialUIContext
and Mui5Context
MaterialComponentContext
(#2724)ui:hideError
featureChangelog
v4.0.1
@rjsf/core
to ^4.0.0
for all of themes in package.json
tagName
prop works as expectedForm
to support the semantic-ui
and material-ui
themes to allow them work when tagName
is providedTheme
and Theme5
implementations to deal with a regression in which adding tagName
caused the 2 themes to not workconsole.log()
the import error in MaterialUIContext
and Mui5Context
when not in production
to eliminate tons of warnings for released codeTheme
implementation to deal with a regression in which adding tagName
caused the theme to not workChangelog
v4.0.0
idSeparator
prop to change the path separator used to generate field names (https://github.com/rjsf-team/react-jsonschema-form/pull/2628)enums
or uniqueItems
support it) (https://github.com/rjsf-team/react-jsonschema-form/pull/2697)@material-ui/core
and @material-ui/icons
to the latest (4.12.0
and 4.11.1
)
MuiForm4
and Theme4
are aliases to the material-ui version 4 MuiForm
and Theme
@material-ui
is not available when one (or both) of the libraries are not installed@mui/material
, @mui/icons-material
, @emotion/react
and @emotion/styled
as optional peer dependenciesMuiForm5
and Theme5
support using the Material UI 5 libraries instead of version 4@mui
is not available when one (or both) of the libraries are not installedChangelog
v3.2.1