Closed anaith1903 closed 1 month ago
Hello @anaith1903! Thanks for opening an issue. The Modus core team will get back to you soon (usually within 24-hours) and provide guidance on how to proceed. Contributors are welcome to participate in the discussion and provide their input on how to best solve the issue, and even submit a PR if they want to.
Please wait until the issue is ready to be worked on before submitting a PR, or you can reach out to the core team if it is time bound. For trivial things, or bugs that don't change the expected behaviors and UI, you can go ahead and make a PR.
Need to make sure that setting the value properly adds the chips. (Also, chip styling is weird)
Prerequisites
Describe the issue
When using Modus autocomplete with multi-select, the component behaves inconsistently based on initialization. If initialized with a single option, it recognizes the value from list of options, allowing further selections. With no initial value, users can select options from the list, which are styled as chips. However, if initialized with multiple options (as a comma-separated list), the component fails to recognize them, displays a "no results found" message, and prevents further selections. Ideally, the autocomplete should recognize comma-separated values from the list, display them as chips, and allow additional selections.
Reduced test cases
https://codepen.io/Anaith-A/pen/KKLdLjO?editors=1010
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
v0.28.0
Priority
High
What product/project are you using Modus Components for ?
Sector portal
What is your team/division name ?
Maps
Are you willing to contribute ?
None
Are you using Modus Web Components in production ?
No response