search

redhat-developer / vscode-openshift-tools

OpenShift extension for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-openshift-connector
MIT License
93 stars 59 forks source link

Bump the rjsf group with 4 updates #4321

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the rjsf group with 4 updates: @rjsf/core, @rjsf/mui, @rjsf/utils and @rjsf/validator-ajv8.

Updates @rjsf/core from 5.19.3 to 5.19.4

Release notes

Sourced from @​rjsf/core's releases.

5.19.4

Security fix

The XSS fix in this release could potentially cause issues if you were using the translateString feature to render HTML. Switching to Markdown will solve your problems.

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Changelog

Sourced from @​rjsf/core's changelog.

5.19.4

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Commits


Updates @rjsf/mui from 5.19.3 to 5.19.4

Release notes

Sourced from @​rjsf/mui's releases.

5.19.4

Security fix

The XSS fix in this release could potentially cause issues if you were using the translateString feature to render HTML. Switching to Markdown will solve your problems.

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Changelog

Sourced from @​rjsf/mui's changelog.

5.19.4

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Commits


Updates @rjsf/utils from 5.19.3 to 5.19.4

Release notes

Sourced from @​rjsf/utils's releases.

5.19.4

Security fix

The XSS fix in this release could potentially cause issues if you were using the translateString feature to render HTML. Switching to Markdown will solve your problems.

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Changelog

Sourced from @​rjsf/utils's changelog.

5.19.4

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Commits


Updates @rjsf/validator-ajv8 from 5.19.3 to 5.19.4

Release notes

Sourced from @​rjsf/validator-ajv8's releases.

5.19.4

Security fix

The XSS fix in this release could potentially cause issues if you were using the translateString feature to render HTML. Switching to Markdown will solve your problems.

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Changelog

Sourced from @​rjsf/validator-ajv8's changelog.

5.19.4

@​rjsf/core

  • Fix XSS when rendering schema validation errors #4254
    • NOTE: This will have potential consequences if you are using the translateString feature and are trying to render HTML. Switching to Markdown will solve your problems.

@​rjsf/utils

  • Updated the ValidatorType interface to add an optional reset?: () => void prop that can be implemented to reset a validator back to initial constructed state
    • Updated the ParserValidator to provide a reset() function that clears the schema map
  • Also updated the default translatable string to use Markdown rather than HTML tags since we now render them with Markdown

@​rjsf/validator-ajv8

  • Updated the AJV8Validator to implement the reset() function to remove cached schemas in the ajv instance

Dev / docs / playground

  • Updated the Validator dropdown to add AJV8 (discriminator) which sets the AJV validator discriminator option to true to support testing schemas with that option in them
Commits


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 commands and options
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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions