Repository navigation
fix: keep continent and location filters searchable - #160
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
2 participants
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.
The continent filter lost its search input because the frontend converted any list with six or fewer choices to a plain menu. Keep city, region, country, continent and timezone filters searchable regardless of option count, including a single available choice.
Opening or typing in the picker does not apply the first continent. Applying Africa updates the normal filtered feed; the mobile check returned 148 jobs across 26 organizations. The existing Africa pillar also renders those jobs.
Validation: type check, lint, targeted regression tests, and a 320px browser check covering opening the picker, typing without navigation, explicit selection and resulting job cards. The release hook runs the production build and full test suite.
ETL investigation: no ETL change needed. Production records show today's import completed at 16:33:48 UTC and its post-import work-arrangement processing completed at 16:34:08. Both mapping and search queues were empty. Existing post-import processing and restart recovery remain in place.