This PR surfaces the necessary APIs for clients to be able to provide their own manual filtering of options in the Select. Additionally, clients can now set a loading-visible attribute on the Select to true to show a visual in the dropdown to indicate that it is in a loading state.
Not in this PR:
Examples that actually exercise the expected client workflow in which they would apply their own custom filtering for options. Instead, there are simply unit tests that validate the necessary notifications for clients to use (in addition to tests regarding the loading visual in the dropdown). The Angular and/or Blazor integration will provide a more complete example of this feature.
๐งช Testing
Unit tests. Chromatic tests.
โ Checklist
[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.
Pull Request
๐คจ Rationale
1866
๐ฉโ๐ป Implementation
This PR surfaces the necessary APIs for clients to be able to provide their own manual filtering of options in the
Select
. Additionally, clients can now set aloading-visible
attribute on theSelect
totrue
to show a visual in the dropdown to indicate that it is in a loading state.Not in this PR:
๐งช Testing
Unit tests. Chromatic tests.
โ Checklist