fix: select components #1052
Merged
fix: select components #1052
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
severinlandolt
approved these changes
May 20, 2024
|
🎉 This PR is included in version 3.17.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Aug 20, 2024
This was referenced Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update items zIndex Add autocomplete prop for SearchSelect Related issue(s) Closes #1051 What kind of change does this PR introduce? (check at least one) [x] Bug fix (non-breaking change which fixes an issue) [ ] New Feature (non-breaking change which adds functionality) [ ] New Feature (BREAKING CHANGE which adds functionality) [ ] Refactor [ ] Build-related changes [ ] Other, please describe: Does this PR introduce a breaking change? (check one) [ ] Yes [x] No If yes, please describe the impact and migration path for existing applications: How has this been tested? Screenshots (if appropriate): The PR fulfils these requirements: [x] It's submitted to the main branch [x] When resolving a specific issue, it's referenced in the related issue section above [ ] My change requires a change to the documentation. (Managed by Tremor Team) [x] I have added tests to cover my changes [x] Check the "Allow edits from maintainers" option while creating your PR. [x] Add refs #XXX or fixes #XXX to the related issue section if your PR refers to or fixes an issue. [x] By contributing to Tremor, you confirm that you have read and agreed to Tremor's CONTRIBUTING.md guideline. You also agree that your contributions will be licensed under the Apache License 2.0 license.