A simple React component capable of using JSON Schema to declaratively build and customize web forms.
Explore the docs »
View Playground · Report Bug · Request Feature
Read our documentation on Read the Docs.
A live playground is hosted on gh-pages.
Read our contributors' guide to get started.
Testing powered by BrowserStack
When I use rjsf out-of-the-box, right after installation I get some unnecessary warnings in the console.
No warnings.
I use rjsf as follows with Material UI version 5.
import { MuiForm5 as Form } from '@rjsf/material-ui';
<Form schema={schema}>
<></>
</Form>
That gives me the following warning in the console:
WARNING in ../../node_modules/@rjsf/material-ui/dist/material-ui.esm.js 1139:21-49
Module not found: Error: Can't resolve '@material-ui/core' in '/... ... .../node_modules/@rjsf/material-ui/dist'
...
WARNING in ../../node_modules/@rjsf/material-ui/dist/material-ui.esm.js 1140:23-52
Module not found: Error: Can't resolve '@material-ui/icons' in '/... ... .../node_modules/@rjsf/material-ui/dist'
From package.json:
"@emotion/react": "^11.7.1",
"@emotion/styled": "^11.6.0",
"@mui/icons-material": "^5.4.4",
"@mui/material": "^5.3.1",
"@rjsf/core": "^4.1.0",
"@rjsf/material-ui": "^4.1.0",
Fix #2555 by adding side-by-side support for both the Material UI 4 and 5 themes as follows:
core to add React 17 as a peer-dependency to support the @mui libraries which requires it
create-react-ref library that didn't support React 17, updating the single usage of it in a test with React.createRef()@material-ui source code
TextFieldProps in favor of simply using the updated WidgetProps in may of the TextField based widgetsMuiComponentContext that will be used for encapsulating the@material-ui or @mui components and icons
@rjsf/material-ui to use the MuiComponentContext to obtain the appropriate Material UI definitions
@rjsf/material-ui IconButton component in favor of explicitly using the Material UI IconButton wrapped around each of the 4 Icons (Add, ArrowDownward, ArrowUpward or Remove)Theme to attempt to load a MaterialUIContext from the @material-ui libraries, which is used in the new Mui4TagName component to wrap a form with a MuiComponentContext for Material UI 4MuiForm5 and Theme5 components that attempt to load a Mui5Context from the @mui libraries, which is used in the new Mui5TagName component to wrap a form with a MuiComponentContext for Material UI 5mui5 tests which are a copy of the version 4 tests except that one failing test was skipped (due to mui issuematerial-ui README.md and a few other theme related documentation filesscreenshot5.png to the root directoryplayground to bump the @material-ui versions and as well as the babel ecosystem and core-js
src/emptyLibrary.js file that simply returns null@mui libraries to return emptyLibrary since trying to load them will break things without React 17playground-r17 package that contains only the core and material-ui themes
react-monoco-editor, monoco-editor and monaco-editor-webpack-plugin to versions that support React 17DemoFrame to use the @emotion/react CacheProvider in addition to the older @material-ui/styles StylesProviderRight now we have no clear way to validate data using anything other then draft-6, which is default for ajv version 5. By updating ajv to newest available version (6.7.0) and making changes listed here: https://github.com/epoberezkin/ajv#using-version-6 we would be able to validate data using other drafts. There are no breaking changes between v5 and v6: https://github.com/epoberezkin/ajv/releases/tag/v6.0.0
npm run cs-format on my branch to conform my code to prettier coding styleRequirements from my design team require the submit buttons to be logically separate in structure, both is usage of React and the DOM. I'm looking for a way to submit and/or validate the form externally or pass in errors that I have validated externally. It doesn't seem possible right now and I couldn't find a way to do it that didn't seem like a complete hack relying on the internals of RJSF.
The following is essentially the crux of the structure. Our design team wants the buttons to be above the form in a header instead of below and the structure of the application prevents wrapping the header inside the form. Any help with the ability to submit/validate/display errors without having buttons as children of the form would be useful.
<div>
<Header>
<button>Submit</button>
<button>Cancel</button>
</Header>
<Form {...formProps}>
<span/>
</Form>
</div>
0.41.2
wontfix possibly closeCurrently there is no options to hide the submit button or change the text of the button. ui:submitButtonProps will allow you to change the text, if it is required for readonly forms and disable it. Fixes https://github.com/rjsf-team/react-jsonschema-form/issues/1602
Because of the changes in way react 17 attaches event listeners, submitting the form programatically no longer works because submit event doesn't bubble.
Solution for this would be to add bubbles: true when dispatching CustomEvent submit.
This is my first pull request and addition to the open-source community. Could you please let me know what else I need to do. My source of inspiration was what was done for rjsf-material-ui project. Because the project was done in typescript, I could not follow the build guide. Could you perhaps assist me with this?
#1537
Bootstrap 4 is out of alpha now...
I don't want rjsf to have to support too much. Ideally we could support either one or zero HTML/CSS frameworks "by default", and the other ones could be added by users in other packages or something. But I think the fact that Bootstrap v3 is now deprecated means the one we support "by default" shouldn't be that. On the other hand, moving unilaterally to a new Bootstrap might be a breaking change for our users. Or maybe it wouldn't be so bad, because it's just a version bump on a dependency in package.json. Thoughts?
Adding support for chakra UI, we're already using this in production for one of our projects, you can get the package here https://github.com/kpilens/rjsf-chakra-ui/packages/492794
If this is related to existing tickets, include links to them as well. Fixes #1640
It's great to be able to define a regex to validate an input, however, that regex should really not be shown to the user. I'd like to be able to define an error string "Your username must only contain letters, numbers and underscores" rather than having it display the regex it isn't matching... no average user can understand what it's looking for from displaying a regex.
As mentioned in https://github.com/mozilla-services/react-jsonschema-form/issues/754 ,
We have a working solution for only returning the data actually used in the form. In addition to the problems stated in the reported issue, we also dont want passthrough unused data, even if we provided it originally. We just want to get the data from whatever is in the visible form. As stated, there is no super straight fwd solution, but we think we found a pretty reasonable and not too intrusive solution.
The idea is....
• Add a name attribute to all of the fields that is the json path to the form data, e.g. foo.bar.1.name (something that IMO should be there regardless of this solution).
• onSubmit we can get all of the form elements and make a list of name attributes (the paths).
• use lodash _.pick(formData, [ARRAY_OF_FIELD_NAMES]) to get only the used data and return that as the formData.
We do this if they set the omitUnusedData prop to true otherwise it defaults to false and works as is.
My coworker @codegains helped me out a bit on this too.
==================
A couple things I wish were better...
~~I wish there was a more reliable way to generate the paths rather than doing string manipulation on the id. But it was hard to access all the necessary data at the point of adding the name attribute.~~
~~The idToPath could fail if the consumer provides a idPrefix prop with an underscore .~~
@codegains update addresses both of the above. no longer an issue
The bonus of having these paths as the name attributes on the fields is that in the future you could potentially simplify your submit and changes with something like https://github.com/maxatwork/form2js (this is super old but basically it gathers formData based on the name attributes more like traditional html forms).
awaiting responseRemove ajv8 alias as it just complicates things, I don't see a benefit to keep it in. This will also address https://github.com/skypackjs/skypack-cdn/issues/337 (which needs to resolved to fix https://github.com/rjsf-team/react-jsonschema-form/issues/3215).
Fix umd builds by adding a default JSONSchemaForm export. This addresses part of the issue of https://github.com/rjsf-team/react-jsonschema-form/issues/3215.
Fixes #3170 by updating types and implementations to support passing uiSchema to the validateFormData() call so that it can be forwarded to customValidate() and transformErrors()
@rjsf/utils, updated the ValidatorType to take the F generic so that validateFormData() can be passed uiSchema?: UiSchema<T, S, F>
F generic and properly adding generics to all the function callsCustomValidator and ErrorTransformer types were updated to take all the generics needed to add the uiSchema?: UiSchema<T, S, F> parameter to the functions@rjsf/validator-ajv6, updated the customizeValidator and AJV6Validator implementations to add the S and F generics
validateFormData() to accept a new optional uiSchema parameter that is passed to transformErrors() and customValidate()@rjsf/validator-ajv8, updated the customizeValidator and AJV8Validator implementations to add the F generic
validateFormData() to accept a new optional uiSchema parameter that is passed to transformErrors() and customValidate()@rjsf/core, updated the ValidatorType, CustomValidator and ErrorTransformer types to add the appropriate missing generics
uiSchema to the validateFormData() callutility-functions.md file to add the new genericstypescript.md file to switch to using customizeValidator() with the generics to get the validatorCHANGELOG.md file accordinglyBumps react-bootstrap from 1.6.5 to 2.7.0.
Sourced from react-bootstrap's releases.
v2.7.0
2.7.0 (2022-12-07)
Bug Fixes
- Dropdown: fic missing .show class on dropdown toggle when active (#6508) (eaa4bb9)
- Modal: fix modal not closing when keyboard=false (#6515) (92703d5)
Features
- AccordionBody: add transition callback props (#6478) (ba092df)
- Dropdown: add support for centered dropdown menus (#6490) (500ee94)
- Ratio: add support for portrait size ratios (#6501) (3cfdab1)
v2.6.0
2.6.0 (2022-11-06)
Bug Fixes
- update
@restart/uito 1.4.0 (#6479) (e38deae)- update
@restart/uito 1.4.1 (#6481) (a42c8de)- ListGroupItem: prevent a div with a href (#6462) (c4b15a3)
- Modal: apply 'show' class when animation = false (#6447) (8f5e903)
- PageItem: remove disabled attribute on span (#6455) (249c178)
- types: fix type of 'safeFindDOMNode' function (#6465) (f2f1847)
Features
v2.5.0
2.5.0 (2022-08-05)
Bug Fixes
- Offcanvas: prevent children mounting twice on show when not responsive (#6416) (e2c4eeb)
- ensure consistent API for custom variants (#6398) (8a81903)
- update
@restart/uito 1.3.1 (#6408) (a49d435)v2.5.0-beta.1
2.5.0-beta.1 (2022-07-08)
Bug Fixes
... (truncated)
Sourced from react-bootstrap's changelog.
2.7.0 (2022-12-07)
Bug Fixes
- Dropdown: fic missing .show class on dropdown toggle when active (#6508) (eaa4bb9)
- Modal: fix modal not closing when keyboard=false (#6515) (92703d5)
Features
- AccordionBody: add transition callback props (#6478) (ba092df)
- Dropdown: add support for centered dropdown menus (#6490) (500ee94)
- Ratio: add support for portrait size ratios (#6501) (3cfdab1)
2.6.0 (2022-11-06)
Bug Fixes
- update
@restart/uito 1.4.0 (#6479) (e38deae)- update
@restart/uito 1.4.1 (#6481) (a42c8de)- ListGroupItem: prevent a div with a href (#6462) (c4b15a3)
- Modal: apply 'show' class when animation = false (#6447) (8f5e903)
- PageItem: remove disabled attribute on span (#6455) (249c178)
- types: fix type of 'safeFindDOMNode' function (#6465) (f2f1847)
Features
2.5.0 (2022-08-05)
Bug Fixes
... (truncated)
cc0e52f Publish v2.7.092703d5 fix(Modal): fix modal not closing when keyboard=false (#6515)847f04a chore(deps): update all non-major dependencies (#6513)96c7bdd chore(deps): bump decode-uri-component from 0.2.0 to 0.2.2 in /www (#6512)3b97f6f chore(deps): bump decode-uri-component from 0.2.0 to 0.2.2 (#6511)212fa9f docs(Button): fix consistent code style in Types example (#6509)ba092df feat(AccordionBody): add transition callback props (#6478)63637e1 chore(deps): bump loader-utils from 1.4.0 to 1.4.2 in /www (#6494)3cfdab1 feat(Ratio): add support for portrait size ratios (#6501)eaa4bb9 fix(Dropdown): fic missing .show class on dropdown toggle when active (#6508)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot merge will merge this PR after your CI passes on it@dependabot squash and merge will squash and merge this PR after your CI passes on it@dependabot cancel merge will cancel a previously requested merge and block automerging@dependabot reopen will reopen this PR if it is closed@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)schema along to the ArrayFieldItemTemplate as part of the fix for #3253onChange handler in the RangeWidget, fixing #2161onChange handler in the RangeWidget, fixing #2161ArrayFieldItemTemplate to add schema as part of the fix for #3253allOfs (#3025, #3227), fixing #2923ErrorSchemaBuilder class to enable building a proper ErrorSchema without crazy castings, fixing #3239ErrorSchemaBuilder in the toErrorSchema() function to simplify the implementationErrorSchemaBuilder in the toErrorSchema() function to simplify the implementationErrorSchema, fixing #3260ArrayFieldItemTemplate as part of the fix for #3253ErrorSchemaBuilder in the utility-functions.md, fixing #3239ref definition to ThemeProps fixing #2135onChange handler in Form to use the new preventDuplicates mode of mergeObjects() when merging extraErrors when live validation is off, fixing #3169computedDefaults (used by getDefaultFormState) to skip saving the computed default if it's an empty object unless includeUndefinedValues is truthy, fixing #2150 and #2708getDefaultFormState util's includeUndefinedValues prop to accept a boolean or "excludeObjectChildren" if it does not want to include undefined values in nested objectsmergeObjects to add new preventDuplicates mode when concatenating arrays so that only unique values from the source object array are copied to the destination object arraymergeObjects() for the new preventDuplicates mode of concatenating arrays@rjsf/validator-ajv8 fixing #3110@rjsf/validator-ajv8 fixing #3110@rjsf/validator-ajv8 fixing #3110false, top or bottom; true is no longer a valid value as the default changed from true to top #634S extends StrictRJSFSchema = RJSFSchema, for schema/rootSchema to every component that needed it.@rjsf/validator-ajv8 fixing #3110F = any generic to be F extends FormContextType = any to better support how formContext is defined and used, partially fixing #3072@rjsf/validator-ajv8 fixing #3110@rjsf/validator-ajv8 fixing #3110@rjsf/validator-ajv8 fixing #3110@rjsf/validator-ajv8 fixing #3110schema/rootSchema to add the generic S extends StrictRJSFSchema = RJSFSchema and use S as the type for them.
StrictRJSFSchema was added as the alias to JSON7Schema and RJSFSchema was modified to be StrictRJSFSchema & GenericObjectTypeF = any generic because it is assumed that more people will want to change the schema than the formContext typesValidatorType interface to add a new rawValidation() method for use by the playgroundFormContextType alias to GenericObjectType and changing the F = any generic to be F extends FormContextType = any to better support how formContext is defined and used, partially fixing #3072RJSFSchema type change@rjsf/validator-ajv8rawValidation() function for use by the playgroundS extends StrictRJSFSchema = RJSFSchema generic and fixed up type castsAjvClass prop to the CustomValidatorOptionsType to support using the Ajv2019 or Ajv2020 class implementation instead of the default Ajv class; fixing #3189rawValidation() function for use by the playground5.x upgrade guide and utility-functions.md to document the new StrictRJSFSchema, the S generic and changing the F generic extendvalidation guide to document the new AjvClass prop on CustomValidatorOptionsType and mentioning the deprecation of @rjsf/validator-ajv6draft-2019-09 and draft-2020-12 schemas and to make the AJV8 validator the default validator, marking AJV6 as deprecated@rjsf/validator-ajv8 validator as the defaultFieldTemplate to no longer render additional, unnecessary white space for fields that have empty help and extra information, fixing #3147ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176FieldTemplate instead of having the widgets implementing the label, fixing #2007ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176chakra-react-select v4, fixing #3152SelectWidget use Select from chakra-react-select for both single- and multiple-choice selectSelectWidget multiple-choice select display label rather than value for selected itemsArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176Form.onChange to optionally return the id of the field that caused the change, fixing #2768additionalProperties was true (#3719).ArrayFieldDescriptionTemplate and ArrayFieldTitleTemplate to not render content when ui:label is false, fixing #2535ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176ArrayFieldTemplate to always render ArrayFieldDescriptionTemplate since that template deals with the optional descriptionschema into the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate, fixing #3176onChange prop on FieldProps and FieldTemplateProps to add an optional id parameter to the callback.DescriptionFieldProps and TitleFieldProps to add a new required schema prop. Also updated the ArrayFieldDescriptionTemplate and ArrayFieldTitleTemplate to make description and title optional while pulling all the other props but id from the associated type.id of the field being changed on the onChange handlerform-props.md to describe the new id parameter being returned by the Form.onChange handlercustom-templates.md to add the new schema prop to the ArrayFieldDescriptionTemplate, ArrayFieldTitleTemplate, DescriptionFieldTemplate and TitleFieldTemplate documentationcontributing.md to describe setting up the husky precommit hooks for the first time git clone of the repo; Also added guidance for developing on underpowered computers; Finally discussed code-coverage requirements for some packages.WrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, protecting against non-arraysantd to Typescript, indirectly fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3123)WrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxWidgets code to eliminate a ternary in favor of a simple inline={inline} property since all the rest of the props were the sameCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, removing unnecessary casts to any and protecting against non-arraysCheckboxesWidget incorrectly rendered inner <form> elements around each checkbox, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2355)WrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, removing unnecessary casts to any and protecting against non-arraysWrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.valueWrapIfAdditionalTemplate. additionalProperties is currently not supported in @rjsf/fluent-ui (See #2777).name or id (for those fluent components not supporting name) to the input components that were missing it to support remixDateTimeWidget to properly use BaseInputTemplate rather than TextWidgetCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, removing unnecessary casts and protecting against non-arrays, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2138)RadioWidget so that it supports read-only and disabled statesWrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, removing unnecessary casts to any and protecting against non-arraysWrapIfAdditional to WrapIfAdditionalTemplatename to the input components that were missing it to support remixCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, removing unnecessary casts to any and protecting against non-arraysWrapIfAdditional to WrapIfAdditionalTemplateArrayFieldTemplate and ObjectFieldTemplate's AddButton to show the non-labeled version. (https://github.com/rjsf-team/react-jsonschema-form/pull/3142)name to the input components that were missing it to support remix, including fixing incorrect names as ids in some situationsCheckboxesWidget and RadioWidget to have unique ids for each radio element by appending the option.value, protecting against non-arrayssemantic-ui to TypescriptWrapIfAdditionalTemplate and WrapIfAdditionalTemplateProps to simplify theming and make it easier to override Field behavior for schemas with additionalProperties.uiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)FieldErrorTemplate to remove the explicit typing of the error to string to support the two optionsTheme to use the renamed ThemeProps from @rjsf/coreuiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)Theme to use the renamed ThemeProps from @rjsf/coreuiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)FieldErrorTemplate to remove the explicit typing of the error to string to support the two optionsvalidateForm() method on Form, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2755, https://github.com/rjsf-team/react-jsonschema-form/issues/2552, https://github.com/rjsf-team/react-jsonschema-form/issues/2381, https://github.com/rjsf-team/react-jsonschema-form/issues/2343, https://github.com/rjsf-team/react-jsonschema-form/issues/1006, https://github.com/rjsf-team/react-jsonschema-form/issues/246)WithThemeProps to ThemeProps to prevent another breaking-change by returning the type back to the name it had in version 4uiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)ArrayField to fall back to SchemaField if ArraySchemaField is not defined, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3131)Theme to use the renamed ThemeProps from @rjsf/coreuiSchema appropriately to all of the IconButtons and ArrayFieldItemTemplate components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)Theme to use the renamed ThemeProps from @rjsf/coreuiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)Theme to use the renamed ThemeProps from @rjsf/coreuiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)FieldErrorTemplate to use the children variation of the List.Item that supports ReactElementuiSchema appropriately to all of the IconButtons, ArrayFieldItemTemplate and WrapIfAdditional components, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)FieldErrorProps type to make it support an array of string and ReactElementIconButtonProps type to add uiSchema, adding the <T = any, F = any> generics to it and the associated ButtonTemplates in TemplatesType AND added uiSchema to ArrayFieldTemplateItemType as well, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3130)custom-templates.md file to add the missing asterisk to the new FieldErrorTemplate and FieldHelpTemplatevalidation.md documentation to describe how to programmatically validate a formchakra-ui custom uiSchema documentation to make it clear they work on a per-field basis, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2865)formElement breaking-change documentation to the 5.x upgrade guide.mdArraySchemaField to better represent the updated implementation, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/3131)FieldErrorTemplate from inside of FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)FieldErrorTemplate and FieldHelpTemplate from inside of FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)FieldErrorTemplate and FieldHelpTemplate from inside of FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)ArraySchemaField, assigned to SchemaField by default, that is used by the ArrayField to render the children for each array field elementErrorList and Help components from inside of SchemaField to new templates: FieldErrorTemplate and FieldHelpTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)FieldErrorTemplate and FieldHelpTemplate from inside of FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)FieldErrorTemplate and FieldHelpTemplate from inside of FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)RawErrors and HelpField into FieldErrorTemplate and FieldHelpTemplate, removing their explicit calls from FieldTemplate; fixes (https://github.com/rjsf-team/react-jsonschema-form/issues/3104)FieldErrorProps and FieldHelpProps typesFieldErrorTemplate and FieldHelpTemplate to the TemplatesTypecustom-templates.md file to add documentation for the new FieldErrorTemplate and FieldHelpTemplatecustom-widgets-fields.md file to add documentation for the new ArraySchemaField field.@rjsf/validator-ajv8 to the validate_test.js file to ensure the validation works with both validator implementationsREADME.md to correct the package name in several places to match the actual packageREADME.md to remove references to ajv6 validator, adding link to the utility-functions.md in the docsREADME.md to correct the package name in several places to match the actual packagegetDefaultFormState() so that oneOf and anyOf default values do not always use the first option when formData contains a better option, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2183)README.md to correct the package name in several places to match the actual packageLocalizer function passed as a second parameter to customizeValidator(), fixing (https://github.com/rjsf-team/react-jsonschema-form/pull/846, and https://github.com/rjsf-team/react-jsonschema-form/issues/1195)README.md to correct the package name in several places to match the actual packageAJV8 and AJV8_es to the list of available validators for the playground; Using the second one will translate error messages to spanish.null in certain cases.devDependencies for React to 17.x and use dts to build and test the library (rather than tsdx)requestSubmit() call to the Form.submit() function, fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2104, https://github.com/rjsf-team/react-jsonschema-form/issues/3023)children property on the FormProps type for Formvalidator prop has not been provided to the FormextraErrors has [] (https://github.com/rjsf-team/react-jsonschema-form/pull/2576).schema.examples in the material ui theme fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2368, https://github.com/rjsf-team/react-jsonschema-form/issues/2557)schema.examples in the material ui theme fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2368, https://github.com/rjsf-team/react-jsonschema-form/issues/2557)schema.examples in the material ui theme fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2368, https://github.com/rjsf-team/react-jsonschema-form/issues/2557)schema.examples in the material ui theme fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2368, https://github.com/rjsf-team/react-jsonschema-form/issues/2557)1.x to 2.x version of semantic-ui-reactschema.examples in the material ui theme fixing (https://github.com/rjsf-team/react-jsonschema-form/issues/2368, https://github.com/rjsf-team/react-jsonschema-form/issues/2557)react-icons (https://github.com/rjsf-team/react-jsonschema-form/pull/3046, https://github.com/react-icons/react-icons/issues/154)playground import error by adding source-map-loader5.x Migration GuideProgrammatic Submit button on the playground form to allow users to test the ability to programmatically submit a formpackage-lock.json files using clean node_modules directories@rjsf/utils library now that it is published on npm@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 messageerrors 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)@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 messageerrors 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)Full Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.2.2...v4.2.3
Source code(tar.gz)Full Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.2.1...v4.2.2
Source code(tar.gz)Full Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.2.0...v4.2.1
Source code(tar.gz)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 themesFull Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.1.1...v4.2.0
Source code(tar.gz)useMuiComponent() hook as a shortcut for useContext(MuiComponentContext)Full Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.0.1...v4.1.1
Source code(tar.gz)toIdSchema() typescript definition to add new idSeparator prop along with the spelling of idPrefix
idSeparator prop through to the AnyOfField and OneOfField inside of SchemaFieldArrayField 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 Mui5ContextMaterialComponentContext (#2724)ui:hideError featureFull Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.0.1...v4.1.0
Source code(tar.gz)@rjsf/core to ^4.0.0 for all of themes in package.jsontagName 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 workFull Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v4.0.0...v4.0.1
Source code(tar.gz)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 installedFull Changelog: https://github.com/rjsf-team/react-jsonschema-form/compare/v3.2.1...v4.0.0
Source code(tar.gz)readonly flag to the Form (https://github.com/rjsf-team/react-jsonschema-form/pull/2554)additionalProperties to falsy values (https://github.com/rjsf-team/react-jsonschema-form/pull/2540)readonly flag to the Form (https://github.com/rjsf-team/react-jsonschema-form/pull/2554)v3 is out, with breaking changes!
See https://react-jsonschema-form.readthedocs.io/en/latest/3.x%20upgrade%20guide/ for more details / an upgrade guide.
Build forms in React, without the tears. Visit https://formik.org to get started with Formik. Organizations and projects using Formik List of organiza
Relay · Relay is a JavaScript framework for building data-driven React applications. Declarative: Never again communicate with your data store using a
nwb nwb is a toolkit for: Quick Development with React, Inferno, Preact or vanilla JavaScript Developing: React Apps Preact Apps Inferno Apps Vanilla
Create React App Create React apps with no build configuration. Creating an App – How to create a new app. User Guide – How to develop apps bootstrapp
redux-form You build great forms, but do you know HOW users use your forms? Find out with Form Nerd! Professional analytics from the creator of Redux
Radium yarn add radium # or npm install --save radium Radium is a set of tools to manage inline styles on React elements. It gives you powerful stylin
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress ?? Looking for v5? The main branch is unde
React Redux Universal Hot Example About This is a starter boilerplate app I've put together using the following technologies: Isomorphic Universal ren
Deprecation Warning This project was started at the advent of the Redux ecosystem, and was intended to help users get up and running quickly. Since th
React Router Declarative routing for React Docs View the docs here Migrating from 2.x/3.x? 3.x docs 2.x docs Packages This repository is a monorepo th
React Redux Official React bindings for Redux. Performant and flexible. Installation Using Create React App The recommended way to start new apps with
A Note from the Author (acdlite, Oct 25 2018): Hi! I created Recompose about three years ago. About a year after that, I joined the React team. Today,
Project Deprecated This project is no longer maintained. For your Redux <-> Router syncing needs with React Router 4+, please see one of these librari
React Apollo ⚠️ THIS PROJECT HAS BEEN DEPRECATED ⚠️ Please note that 4.0.0 is the final version of all React Apollo packages. React Apollo functionali
You build great forms, but do you know HOW users use your forms? Find out with Form Nerd! Professional analytics from the creator of React Final Form.
RefluxJS A simple library for unidirectional dataflow architecture inspired by ReactJS Flux. Installation You can currently install the package as a n
react-responsive Information Package react-responsive Description Media queries in react for responsive design Browser Version >= IE6* Demo The best s
React CSS Modules React CSS Modules implement automatic mapping of CSS modules. Every CSS class is assigned a local-scoped identifier with a global un
mobx-react ?? ?? ?? This repo has been moved to mobx Package with React component wrapper for combining React with MobX. Exports the observer decorato
31.8k Jan 8, 2023
17.5k Dec 29, 2022
5.5k Dec 21, 2022
12.6k Dec 27, 2022
7.4k Jan 1, 2023
38k Dec 30, 2022
12.1k Jan 7, 2023
10.3k Dec 23, 2022
49.3k Jan 8, 2023
22.5k Jan 5, 2023
14.8k Dec 23, 2022
7.9k Dec 30, 2022
6.9k Jan 7, 2023
7.2k Jan 6, 2023
5.4k Dec 21, 2022
6.5k Jan 5, 2023
5.3k Dec 28, 2022
4.9k Jan 4, 2023