Repository navigation
feat(growth): recover from empty catalog searches without losing users - #66
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.
Adds an accessible 'Clear search and filters' control when a catalog query + purpose filter yields zero apps. The control clears search text, resets to All apps, resets the search instrumentation guard, restores results, focuses the search field and emits only a non-PII
catalog_search_resetevent. This helps users recover instead of abandoning the catalog. No store card packages, existing event names, catalog JSON-LD, or five app detail links changed. Extends live smoke with reset-control and handler checks and two negative regression tests. 27/27 Python unittests passed locally on branch-identical blob contents: check_growth_live.pya82647843fab435be068cf0ad0d8f1ffedae9abb, test_growth_live.py99de2cb819f621b1af72efc6ca8de286adfb634e. No GitHub Actions, production deployment or evidence of retention uplift.