Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce new "Select" lineup #1537

Closed
mimarz opened this issue Sep 2, 2021 · 0 comments
Closed

Introduce new "Select" lineup #1537

mimarz opened this issue Sep 2, 2021 · 0 comments
Assignees
@mimarz
Labels
epic

Comments

@mimarz
Copy link
Contributor

mimarz commented Sep 2, 2021 •
edited
Loading

Summary

After todays meeting with @akvam @vnys @BirteThornquist and @mimarz on 02.09.2021. We decided to do some changes to clarify our "select" components.

Today we have MultiSelect, SingleSelect & NativeSelect. In reality both MultiSelect & SingleSelect are a Combobox and we are missing a "normal" Select.

I we also want to introduce FR #1430 & #1416 we will have also to do breaking changes in both MultiSelect & SingleSelect

Actions

  1. We will introduce a new component Autocomplete which will replace both MultiSelect & SingleSelect. The new component will have a flag or built in predicate for when multi support is activated.
  2. A "normal" Select will be introduced.
  3. MultiSelect & SingleSelect will still be available along Autocomplete but deprecated in a future release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mimarz mimarz

Labels
epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mimarz @akvam