[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
Which package are you modifying?
[ ] accordion
[ ] alert
[ ] alert-dialog
[ ] aspect-ratio
[ ] avatar
[ ] badge
[ ] button
[ ] calendar
[ ] card
[ ] checkbox
[ ] collapsible
[ ] combobox
[ ] command
[ ] context-menu
[ ] data-table
[ ] date-picker
[ ] dialog
[ ] dropdown-menu
[ ] hover-card
[ ] icon
[ ] input
[ ] label
[ ] menubar
[ ] navigation-menu
[ ] pagination
[ ] popover
[ ] progress
[ ] radio-group
[ ] scroll-area
[ ] select
[ ] separator
[ ] sheet
[ ] skeleton
[ ] slider
[ ] sonner
[ ] spinner
[ ] switch
[ ] table
[ ] tabs
[ ] textarea
[ ] toast
[ ] toggle
[ ] tooltip
[ ] typography
What is the current behavior?
The value bound to [(ngModel)] is not displayed correctly in the control if it is not a string or a array.
When multiple is true and a value is provided via ngModel
When then addtional option is selected, the first options are not checked anymore.
In this example, 1,3 are preselected by ngModel and 4 was clicked.
Closes #237
What is the new behavior?
Values set by ngModel are set correctly also when it is a number.
For multiple Select, the initialValues are set always when the Value changes from the ControlValueAccessor, because otherwise, Values would not be set correct if additional options are selected.
multiple selections are not cleared after selecting additional option
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
The value bound to [(ngModel)] is not displayed correctly in the control if it is not a string or a array.
When multiple is true and a value is provided via ngModel When then addtional option is selected, the first options are not checked anymore. In this example, 1,3 are preselected by ngModel and 4 was clicked.
Closes #237
What is the new behavior?
Values set by ngModel are set correctly also when it is a number.
For multiple Select, the initialValues are set always when the Value changes from the ControlValueAccessor, because otherwise, Values would not be set correct if additional options are selected.
Does this PR introduce a breaking change?
Other information