Skip to content

feat(typeahead): support typeaheadLoading via input#1637

Draft
spike-rabbit wants to merge 1 commit intomainfrom
feat/typeahead/loading-input
Draft

feat(typeahead): support typeaheadLoading via input#1637
spike-rabbit wants to merge 1 commit intomainfrom
feat/typeahead/loading-input

Conversation

@spike-rabbit
Copy link
Member

@spike-rabbit spike-rabbit commented Mar 13, 2026

The current optionSource approach is not feasible for the filtered-search in its current situation. So we need an alternative.

This is also flagged as experimental, hoping that with ongoing filtered-search refactoring, we may get rid of that.


Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

The current `optionSource` approach is not feasible for the filtered-search
in its current situation. So we need an alternative.

This is also flagged as experimental, hoping that with ongoing
filtered-search refactoring, we may get rid of that.
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request refactors the loading state management within the si-typeahead component and directive. It introduces a new typeaheadLoading input property to allow external control over the loading state and a optionSourceLoading signal to manage internal loading from the option source. These two signals are combined into a new loading computed signal, which is then used in the component's template to display loading indicators. The previous internal typeaheadLoading signal has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant