We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When MultiSchemaField is part of an array the idSchema is incorrectly generated. This can cause duplicated ids.
packages/core/test/anyOf_test.js
should correctly render form inputs for anyOf inside array items
input#root_foo
The idSchema ids should maintain the full id even if they're inside arrays.
For example, given a schema
const schema = { type: "object", properties: { items: { type: "array", items: { type: "object", anyOf: [ { properties: { foo: { type: "string", }, }, }, { properties: { bar: { type: "string", }, }, }, ], }, }, }, };
The id for the foo field within each array item should be root_items_0_foo, root_items_1_foo etc.
foo
root_items_0_foo
root_items_1_foo
For the example above, the generated id is root_foo for all array items.
root_foo
2.4.1
The text was updated successfully, but these errors were encountered:
Fixed in v5 beta via #3039, see the 5.x migration guide
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Prerequisites
Description
When MultiSchemaField is part of an array the idSchema is incorrectly generated. This can cause duplicated ids.
Steps to Reproduce
packages/core/test/anyOf_test.js
should correctly render form inputs for anyOf inside array items
input#root_foo
to exist, but that's not the right idExpected behavior
The idSchema ids should maintain the full id even if they're inside arrays.
For example, given a schema
The id for the
foo
field within each array item should beroot_items_0_foo
,root_items_1_foo
etc.Actual behavior
For the example above, the generated id is
root_foo
for all array items.Version
2.4.1
The text was updated successfully, but these errors were encountered: