Add schemaPath to errors object in transformErrors #1140
Closed
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
Fix for non-standard file names (with spaces, apostrophes, etc) that prevent to be used.
|
I'm getting this test failure, not sure why |
rjsf-team#1142) * rjsf-team#556 - handle recursive references to deep schema definitions * test: add tests for recursive references * fix: handle multiple recursive references to deep schema definitions
…jsf-team#1131) * Add test and update documentation for using anyOf inside array items Signed-off-by: Lucian <lucian.buzzo@gmail.com>
* add ui:help tips from rjsf-team#743 (comment)
…am#1143) * fix: add onBlur and onFocus events for radio and checkbox widgets * fix: use event.target.checked instead of event.target.value for checkbox
…eam#1129) This change improves the logic that selects a matching anyOf branch based on form data. Previously the behaviour was to just check if the form data was valid against an anyOf branch, however due to the permissive nature of JSON schema this has unexpected behaviour. For example, given the following schema: ```json { "type": "object", "anyOf": [ { "properties": { "foo": { "type": "string" } } }, { "properties": { "bar": { "type": "string" } } } ] } ``` The form data `{ bar: 'baz' }` will actually match the first branch. To mitigate this, when doing the matching, the branch schema is augmented to require at least one of the keys in the branch. For example the schema above would become: ```json { "type": "object", "anyOf": [ { "properties": { "foo": { "type": "string" } }, "anyOf": [ { "required": [ "foo" ] } ] }, { "properties": { "bar": { "type": "string" } }, "anyOf": [ { "required": [ "bar" ] } ] } ] } ``` Signed-off-by: Lucian <lucian.buzzo@gmail.com>
* Fixes rjsf-team#824 * Added test * Separated tests
* fix: uiSchema for additionalProperties rjsf-team#1132 * doc: update readme * doc: fix toc * doc: update docs
…efault value is 0 or false or ''.
|
I guess it's because |
This change adds support for schemas that use the `const` keyword
without and adjacent `type` keyword. For example:
```json
{
"type": "object",
"properties": {
"firstName": {
"const": "Chuck"
}
}
}
```
Signed-off-by: Lucian <lucian.buzzo@gmail.com>
…eam#1171) Change-type: patch Signed-off-by: Lucian <lucian.buzzo@gmail.com>
Change-type: patch Signed-off-by: Lucian <lucian.buzzo@gmail.com>
…jsf-team#1169) * Fix multiple bugs related to switching between anyOf/oneOf options Fixes rjsf-team#1168 - Fixed a bug that would prevent input fields from rendering when switching between a non-object type option and an object type option - Fixed a bug where options would incorrectly change when entering values if a subschema with multiple required fields is used - Fixed a bug where switching from an object tpye option to a non-object type option would result in an input field containing the value [Object object] Change-type: patch Signed-off-by: Lucian <lucian.buzzo@gmail.com> * Update src/utils.js * Update src/utils.js
Followup to f62cfc4 which broke the build:readme script
…aa/react-jsonschema-form into huhuaaa-feature/fix-enum-empty-bug
epicfaace
commented
Feb 23, 2019
epicfaace
commented
Feb 23, 2019
16 tasks
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
Fixes #838 by exposing
schemaPathin the items in theerrorslist.Also documents the objects in the
errorslist to fix #818 .If this is related to existing tickets, include links to them as well.
Checklist
npm run cs-formaton my branch to conform my code to prettier coding style