Repository navigation
refactor: extract SearchProductsUseCase from SearchViewModel for SRP … - #11
Merged
Merged
Conversation
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.
…compliance
refactor: extract SearchProductsUseCase
Follow-up to feature/search. Moves filter-matching logic (title/category
substring match) out of SearchViewModel into a new domain use case,
SearchProductsUseCase, for SRP compliance — ViewModel should orchestrate
state, not own business rules about what constitutes a search match.
Test suite split accordingly: SearchProductsUseCaseTest covers matching
correctness in isolation (no mocking needed), SearchViewModelTest now mocks
the use case and covers only ViewModel-level concerns (debounce timing,
state transitions, recent searches, effects).
No behavior change from a user's perspective — this is a pure architecture
improvement.