-
Notifications
You must be signed in to change notification settings - Fork 347
Fix bug where loading saved search from another page #1563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug where loading saved search from another page #1563
Conversation
…t values instead - also adds tests for the scenario Fixes HDX-3149
🦋 Changeset detectedLatest commit: 7c1c27f The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code Review✅ No critical issues found. The implementation correctly addresses the saved search state management bug. Key improvements:
Minor observations (non-blocking):
|
E2E Test Results✅ All tests passed • 59 passed • 4 skipped • 740s
Tests ran across 4 shards in parallel. |
pulpdrew
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes a bug where loading a saved search page from another non-search page may result in the default select/order by being used instead of the saved search values.
Attempts to make these types of errors happen less by creating a new
defaultSearchConfigobject which represents the default values to fallback on (currently it was mixing concerns in a few places)also adds tests for the scenario
Fixes HDX-3149