feat(search-client): replace input output decorator technique with signals - #77
Merged
Conversation
yeshamavani
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request refactors the
SearchComponentin the Angular search library to use Angular's new signal-basedinputandoutputAPIs, and replaces direct property access with computed signals throughout the component and its template. This modernizes the component, improves reactivity, and simplifies input/output handling. Several internal methods and template bindings are updated to use the new reactive patterns, and legacy input/output decorators and setters are removed.Key changes include:
Migration to Angular Signals:
Replaced all
@Inputand@Outputdecorators insearch.component.tswith the newinput()andoutput()signal-based APIs, and removed legacy setters/getters. All references to configuration and templates in the component and template now use computed signals (e.g.,cfg(),titleTemplate()). [1] [2] [3]Updated the component's logic to use
effect()for reacting to changes in inputs, such as updating models, adapting the search provider, and handling custom search events.Fixes #61
Type of change
Please delete options that are not relevant.
Checklist: