Releases: csandman/chakra-react-select
Releases · csandman/chakra-react-select
3.3.10
What's Changed
- Fix for V3: Prevent a selected option from being removed when isDisabled is passed by @lschlesinger in #302
New Contributors
- @lschlesinger made their first contribution in #302
Full Changelog: v3.3.9...v3.3.10
4.7.6
4.7.5
What's Changed
- fix: Fix module augmentation and install latest version of
react-select
again by @csandman in #292- This is a real fix for #273, meaning
chakra-react-select
is no longer stuck on an older version ofreact-select
!
- This is a real fix for #273, meaning
Full Changelog: v4.7.4...v4.7.5
4.7.4
4.7.3
What's Changed
- fix: Attempt to update for projects using
moduleResolution="bundler"
by downgrading react-select by @csandman in #284
This version is a temporary fix to issue #273. It downgrade the react-select dependency version to v5.7.0
to ensure that the custom props work for all users. Once my PR gets merged into the base package, this package will be re-upgraded to the newest version. See this PR for full details.
Full Changelog: v4.7.2...v4.7.3
4.7.2
- Closes #281 -
useBasicStyles
was no longer defined.
Full Changelog: v4.7.1...v4.7.2
4.7.1
What's Changed
- fix: import chakraui/icon by @jonashger in #277
- This fixed an issue #276, in which the export of
Icon
from@chakra-ui/icon
changed from a default export to a named export inv3.2.0
. Thanks to @jonashger for the quick fix, but I went one step further here and removed the dependency on@chakra-ui/icon
from theMenu
file in general by switching to using the native<svg>
, like they do in the originalMenu
component.
- This fixed an issue #276, in which the export of
New Contributors
- @jonashger made their first contribution in #277
Full Changelog: v4.7.0...v4.7.1
4.7.0
What's Changed
- chore: Update packages and simplify
ThemeObject
type by @csandman in #257 - fix: Add Chakra Menu to provide context for MenuIcon dependency by @malinskibeniamin in #269
- chore: Update all dependencies by @csandman in #270
- This PR also fixes some style issues that are caused by
@chakra-ui/react@2.8.0
, specifically@chakra-ui/theme@3.2.0
in which the theme styles for theInput
component were changed, breaking the way they were being used by this package. This change should be backwards compatible with the other 2.x.x versions of Chakra.
- This PR also fixes some style issues that are caused by
New Contributors
- @malinskibeniamin made their first contribution in #269
Full Changelog: v4.6.0...v4.7.0
4.6.0
What's Changed
- Value Style Fixes by @csandman in #248
- Fix various styles, so they line up better with how the original
react-select
is laid out- In response to #246
- Fix the condition for setting the
aria-invalid
prop
- Fix various styles, so they line up better with how the original
- Prop Deprecation by @csandman in #247
- Add
@deprecated
flags to both the originalstyles
andtheme
props to help prevent people from using them by mistake.- Unfortunately, these props are not flagged when you attempt to pass them into the component, but at least the
@deprecated
label shows up when you hover over the prop.
- Unfortunately, these props are not flagged when you attempt to pass them into the component, but at least the
- Change the prop
selectedOptionColor
toselectedOptionColorScheme
to prevent confusion.- The
selectedOptionColor
prop will still function for the time being, but will be removed in the next major version
- The
- Remove the documentation for
hasStickyGroupHeaders
andisFixed
as a soft deprecation. They still function for now, but will probably be removed eventually (unless people start complaining).- These props were added very early on in this package's development, mostly as a way to try some things myself. Ultimately, they don't make much sense in the scope of other props, and these same customizations can be done from the user's side with custom
components
andchakraStyles
.
- These props were added very early on in this package's development, mostly as a way to try some things myself. Ultimately, they don't make much sense in the scope of other props, and these same customizations can be done from the user's side with custom
- Add
Full Changelog: v4.5.0...v4.6.0
4.5.0
What's Changed
- Fixed grammar and spelling mistakes in README.md by @JackHumphries9 in #217
- Make the
size
prop responsive by @csandman in #243- Make the
size
prop responsive, so either a breakpoint object or array can be passed in addition to a normal value.- Feature added in response to #241.
- Also added the
@chakra-ui/media-query
package in order to accomplish this.
- Update all packages.
- Make the
- Custom Variants by @csandman in #244
- Add the option to use custom variants for the
Input
andTag
components, pulled from the theme. This feature isn't widely tested and may not perform exactly how you expect it to.- Closes #215
- Add the option to use custom variants for the
New Contributors
- @JackHumphries9 made their first contribution in #217
Full Changelog: v4.4.3...v4.5.0