dependabot[bot] opened a new pull request, #45004: URL: https://github.com/apache/superset/pull/45004
Bumps the rjsf group in /superset-frontend with 3 updates: [@rjsf/core](https://github.com/rjsf-team/react-jsonschema-form), [@rjsf/utils](https://github.com/rjsf-team/react-jsonschema-form) and [@rjsf/validator-ajv8](https://github.com/rjsf-team/react-jsonschema-form). Updates `@rjsf/core` from 6.10.1 to 6.11.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/core's releases</a>.</em></p> <blockquote> <h2>6.11.0</h2> <h1>New feature</h1> <ul> <li><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/form-props/#requiredbooleandefault";>requiredBooleanDefault</a> was added to the <code>Experimental_DefaultFormStateBehavior</code></li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/core's changelog</a>.</em></p> <blockquote> <h1>6.11.0</h1> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4aeb5fa83d27f262e352510b5ff151a0bab241e2";><code>4aeb5fa</code></a> Releasing 6.11.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/ec97e497658ce1f794e63e3b5fb644811f3fe49c";><code>ec97e49</code></a> Fix 4476: restore an option's defaults when switching oneOf/anyOf (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5335";>#5335</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b1e39dc1f4d1d94c48be30268fa31c6299fe4c97";><code>b1e39dc</code></a> feat(utils): add requiredBooleanDefault option to opt out of the required-boo...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4d1cb92af85f0601a97eedef4c5eb72a9eef1946";><code>4d1cb92</code></a> Fix <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a>: apply schema changes that add a defaulted property after onChange ...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/3002e47912943dfd100a7ecbe266074895e38a97";><code>3002e47</code></a> chore(deps): bump ata-validator to ^1.23.0 in <code>@rjsf/validator-ata</code> (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5293";>#5293</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/9ee0673fa1a098d5a056877ec95313beb0440600";><code>9ee0673</code></a> Releasing 6.10.1 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5291";>#5291</a>)</li> <li>See full diff in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.10.1...v6.11.0";>compare view</a></li> </ul> </details> <br /> Updates `@rjsf/utils` from 6.10.1 to 6.11.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/utils's releases</a>.</em></p> <blockquote> <h2>6.11.0</h2> <h1>New feature</h1> <ul> <li><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/form-props/#requiredbooleandefault";>requiredBooleanDefault</a> was added to the <code>Experimental_DefaultFormStateBehavior</code></li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/utils's changelog</a>.</em></p> <blockquote> <h1>6.11.0</h1> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4aeb5fa83d27f262e352510b5ff151a0bab241e2";><code>4aeb5fa</code></a> Releasing 6.11.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/ec97e497658ce1f794e63e3b5fb644811f3fe49c";><code>ec97e49</code></a> Fix 4476: restore an option's defaults when switching oneOf/anyOf (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5335";>#5335</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b1e39dc1f4d1d94c48be30268fa31c6299fe4c97";><code>b1e39dc</code></a> feat(utils): add requiredBooleanDefault option to opt out of the required-boo...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4d1cb92af85f0601a97eedef4c5eb72a9eef1946";><code>4d1cb92</code></a> Fix <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a>: apply schema changes that add a defaulted property after onChange ...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/3002e47912943dfd100a7ecbe266074895e38a97";><code>3002e47</code></a> chore(deps): bump ata-validator to ^1.23.0 in <code>@rjsf/validator-ata</code> (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5293";>#5293</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/9ee0673fa1a098d5a056877ec95313beb0440600";><code>9ee0673</code></a> Releasing 6.10.1 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5291";>#5291</a>)</li> <li>See full diff in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.10.1...v6.11.0";>compare view</a></li> </ul> </details> <br /> Updates `@rjsf/validator-ajv8` from 6.10.1 to 6.11.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/validator-ajv8's releases</a>.</em></p> <blockquote> <h2>6.11.0</h2> <h1>New feature</h1> <ul> <li><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/form-props/#requiredbooleandefault";>requiredBooleanDefault</a> was added to the <code>Experimental_DefaultFormStateBehavior</code></li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/validator-ajv8's changelog</a>.</em></p> <blockquote> <h1>6.11.0</h1> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed a <code>schema</code> prop change being silently dropped when it adds a property with a <code>default</code>, either as the parent's reply to <code>onChange</code> or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own <code>formData</code> (an uncontrolled form, or a parent holding what <code>onChange</code> emitted, including when it reshaped the emitted value by spreading it, storing <code>undefined</code> as <code>null</code> or round-tripping it through JSON) with the same <code>schema</code> and <code>experimental_defaultFormStateBehavior</code>, and it keeps only that <code>formData</code> rather than dropping the rest of the prop update, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a></li> <li>Fixed switching between <code>oneOf</code>/<code>anyOf</code> options keeping a value the previous option's <code>default</code> put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's <code>default</code> the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new <code>default</code> up as well instead of arriving empty — one whose type differs between the options, or a <code>readOnly</code> one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in <code>formData</code>, since the two cannot be told apart, fixing <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/4476";>#4476</a></li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Updated <code>Experimental_DefaultFormStateBehavior</code> to add a new <code>requiredBooleanDefault</code> option, and updated <code>getDefaultFormState()</code> to honor it: <code>skip</code> turns off the <code>false</code> populated for a required boolean with no <code>default</code> (introduced in 6.9.0 by <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5170";>#5170</a>), so a form that models an unanswered boolean as its own state can keep it <code>undefined</code> and let <code>required</code> report it. The default, <code>populateFalse</code>, keeps the 6.9.0+ behavior</li> </ul> <h2><code>@rjsf/validator-ata</code></h2> <ul> <li>Updated <code>ata-validator</code> from <code>^1.7.1</code> to <code>^1.23.0</code>, picking up the corrected error shape for <code>unevaluatedProperties</code> (the error now carries <code>params.unevaluatedProperty</code>), the removal of a quadratic in <code>additionalProperties: false</code> schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/pull/5293";>#5293</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented the <code>requiredBooleanDefault</code> option in <code>form-props.md</code> and <code>internals.md</code>, and added a selector for it to the playground</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4aeb5fa83d27f262e352510b5ff151a0bab241e2";><code>4aeb5fa</code></a> Releasing 6.11.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/ec97e497658ce1f794e63e3b5fb644811f3fe49c";><code>ec97e49</code></a> Fix 4476: restore an option's defaults when switching oneOf/anyOf (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5335";>#5335</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b1e39dc1f4d1d94c48be30268fa31c6299fe4c97";><code>b1e39dc</code></a> feat(utils): add requiredBooleanDefault option to opt out of the required-boo...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/4d1cb92af85f0601a97eedef4c5eb72a9eef1946";><code>4d1cb92</code></a> Fix <a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5294";>#5294</a>: apply schema changes that add a defaulted property after onChange ...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/3002e47912943dfd100a7ecbe266074895e38a97";><code>3002e47</code></a> chore(deps): bump ata-validator to ^1.23.0 in <code>@rjsf/validator-ata</code> (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5293";>#5293</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/9ee0673fa1a098d5a056877ec95313beb0440600";><code>9ee0673</code></a> Releasing 6.10.1 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5291";>#5291</a>)</li> <li>See full diff in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.10.1...v6.11.0";>compare view</a></li> </ul> </details> <br /> 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`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
