Bump chakra-react-select from 3.3.10 to 5.0.2 in /clients/admin-ui

[dependabot]

Bumps chakra-react-select from 3.3.10 to 5.0.2.

Release notes

Sourced from chakra-react-select's releases.

5.0.2

What's Changed

Mostly some documentation/CI changes, along with a new build config.

• feat: Add a demo vite app by @​csandman in csandman/chakra-react-select#344
  • Added a new local demo app for testing. See the Contributing doc for more info.
  • Added a new build action for previewing PR changes.
• Improve the exports and modify the tsup build config by @​csandman in csandman/chakra-react-select#346
  • Update exports to include specific types paths for import and require.
  • Changed build config to stop minifying the output and building source maps.

Full Changelog: csandman/chakra-react-select@v5.0.1...v5.0.2

5.0.1

What's Changed

• Removes support for the isFixed attribute on options to remove the tag close button. This was supposed to be removed with the other breaking changes, but it was missed.
  • The original idea for this feature was taken from an example in the react-select docs for how you can use custom components. Because of this, this should be done by the end user if desired.

Full Changelog: csandman/chakra-react-select@v5.0.0...v5.0.1

5.0.0

What's Changed

This is the last major release before Chakra v3 is fully released! The intention of this release is to batch a few breaking changes that have been in the works for a while, along with a codemod to hopefully make the changes for you.

Breaking Changes

1. The useBasicStyles prop was removed, as the styles provided by it are now the default. Originally, it was styled to match the InputRightAddon component, in order to create a visual separation between the dropdown indicator and the clear indicator. However, it seems that most people preferred it to visually match the original Chakra Select component, so those styles are now the default. If you want to modify the styles to appear like they used to, you can do so using the chakraStyles prop. Some examples of how to do this are provided in the README.
2. Remove the deprecated selectedOptionColor prop. A new prop was added a while ago to replace that one, selectedOptionColorScheme, as some people were getting confused by the meaning of the original (thinking it meant an explicit color instead of a named color from their theme). The old one was left in the code though, and now it is gone for good.
3. Remove the deprecated hasStickyGroupHeaders prop. This was removed from the documentation since v4.6.0, as it was only ever really an experimental way to style the grouped option headers so they'd stay in view while you scroll the list of options. It also had some problems with using the keyboard to navigate between options. They would disappear behind the header when you used the up arrow. There is an example for how these styles can be implemented using chakraStyles in #343.
4. Renamed the colorScheme prop to tagColorScheme. There has been some confusion around what this prop actually means, as the original name the prop had wasn't specific enough to it's purpose. It didn't make sense to have a specific prop for selectedOptionColorScheme, and not be specific with the naming for the tagColorScheme. This may be followed by the addition of a new root colorScheme prop, but that isn't included here.

All of these changes can be made automatically using the Codemod provided here

npx crs-codemod@latest v5 .
# or
npx crs-codemod@latest v5 ./src

---

This release will most likely mean an end of support for v3 (Chakra v1 compatible version), unless people want to put up any fix PRs for it themselves.

Full Changelog: csandman/chakra-react-select@v4.10.1...v5.0.0

4.10.1

... (truncated)

Commits

• d524a2c 5.0.2
• e8916bb Merge pull request #346 from csandman/exports-and-build
• 765b644 Update deprecated docs
• a703fe3 Stop minifying build
• c4ff9d1 Update package.json exports field to properly export types for each build type
• 7f4b743 Merge pull request #344 from csandman/feat/demo
• e896665 Remove --only-templates
• 41d1dc0 Try --only-templates
• ddabe15 One more readme cleanup
• e855b01 Some more readme cleanup
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 13, 2024 9:50pm