Releases: csandman/chakra-react-select
5.1.0
What's Changed
- v5: Update all dependency versions by @csandman in #372
- feat: Update default menu placement to
"auto"by @csandman in #373
This change is to match the default flipping behavior of all Chakra UI popovers out of the box, and to align with the behavior in v6. This could be seen as a "breaking" change to some if you were reliant on the old behavior, so if you want to go back to the old behavior of having the select menu always stay below the input, pass the prop menuPlacement="bottom" to your select.
Full Changelog: v5.0.5...v5.1.0
6.1.1
5.0.5
6.1.0
What's Changed
- feat: Change
selectedOptionColorPalettevalues pulled from the theme by @csandman in #364- Instead of using
colorPalette.300andcolorPalette.500for the selected option background colors, the semantic tokencolorPalette.solidwill be used instead. And for the option label, the text color will becolorPalette.contrast.
- Instead of using
- Update type definitions for color palette props to allow for more than just the generated
ColorPalettetype by @saalto-it in #362 - Update all dependencies in main package and demo by @csandman in #363
- [ImgBot] Optimize images by @imgbot in #365
New Contributors
- @saalto-it made their first contribution in #362
Full Changelog: v6.0.1...v6.1.0
5.0.4
5.0.3
What's Changed
- [v5] Libraries - Update react-select to 5.10.0 by @rmanganiello in #357
- chore: Update dev dependencies by @csandman in #358
New Contributors
- @rmanganiello made their first contribution in #357
Full Changelog: v5.0.2...v5.0.3
6.0.1
6.0.0
Finally, a Chakra V3 compatible version of Chakra React Select is ready to go! There were many breaking changes in the V3 release of Chakra UI, so this version took a while, but it's now ready for use in production. Thanks to everyone who tested out the pre-releases and gave feedback.
The docs should be fully updated, but if anything doesn't make sense after the release, don't hesitate to post an issue or a discussion. Unfortunately, due to the size of this release, there won't be a codemod available for migrating (similar to the core Chakra library). Here are all of the breaking changes that should be noted when upgrading.
Breaking Changes
- Most of the styles pulled from the theme are now using styles from Chakra's new
Selectcomponent.- The exceptions are the
Control, which still uses styles from theInputtheme, and theMultiValuecomponents, which still pull their styles from theTagtheme. The docs have been updated to list out which theme styles are being used for each React Select sub-component: https://github.com/csandman/chakra-react-select#theme-styles.
- The exceptions are the
- Everything that was previously named
colorSchemeis now namedcolorPalette: https://www.chakra-ui.com/docs/get-started/migration#colorscheme-proptagColorSchemeis nowtagColorPalette.selectedOptionColorSchemeis nowselectedOptionColorPalette.- An individual option's
colorSchemekey is nowcolorPalette.
- Some props were replaced on
chakraComponents.LoadingIndicator:emptyColoris nowtrackColor(this isn't a real prop, but it maps to the--spinner-track-colorcss variable).speedis nowanimationDuration.thicknessis nowborderWidth.- The prop
colorPalettewas also added to the loading indicator which can be used to set the color without specifying a token number (responds better to changes between light and dark mode).
- The
LoadingIndicatorcomponent no longer changes size in response to changes to the rootsizeprop. With the new default size, the default spinner size ended up looking the best across all three select sizes. focusBorderColorwas replaced withfocusRingColoranderrorBorderColorwas removed, as there is no longer any equivalent prop that exists.- All boolean props have had the
isprefix removed: https://www.chakra-ui.com/docs/get-started/migration#boolean-propsisRequiredis now therequiredattribute that's already built-in toreact-select. It will behave the same as therequiredprop on any other Chakra component.isReadOnlyis nowreadOnlyisInvalidis nowinvalid. This prop was removed from the coreInput,Select, andTextareacomponents in the Chakra UI library in favor of passing them into a wrappingField.Root. However, they were left on this package due to many users not always wrapping theSelect: https://www.chakra-ui.com/docs/get-started/migration#input-select-textarea- Adds
disabled, which will override theisDisabledprop built-in toreact-select- This is just to keep the props consistent with the other Chakra prop names. The
isDisabledprop from React Select will still function as it did previously.
- This is just to keep the props consistent with the other Chakra prop names. The
- Add a default for the
menuPlacementof"auto". This is to more closely match the default flipping behavior of the ChakraSelect.
One other change to note is that most of the other custom StackBlitz demos were removed from the readme. These were very time consuming to maintain, so they were removed to prevent confusion. However, most of the advanced examples were added to the main demo, so if you'd like to see how any of them have changed, you can check there.
The main demo is now a direct copy of the demo project included in this repo. This should make maintenance much easier going forward, as this will always be the basis for testing future changes.
Full Changelog: v5.0.2...v6.0.0
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 #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
exportsand modify the tsup build config by @csandman in #346- Update exports to include specific types paths for
importandrequire. - Changed build config to stop minifying the output and building source maps.
- Update exports to include specific types paths for
Full Changelog: v5.0.1...v5.0.2
5.0.1
What's Changed
- Removes support for the
isFixedattribute 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-selectdocs for how you can use custom components. Because of this, this should be done by the end user if desired.
- The original idea for this feature was taken from an example in the
Full Changelog: v5.0.0...v5.0.1