Skip to content
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

Improve bulk search UI #847

Merged
merged 3 commits into from
Sep 25, 2024
Merged

Improve bulk search UI #847

merged 3 commits into from
Sep 25, 2024

Conversation

felixclack
Copy link
Contributor

We can improve the UX of the bulk search experience by adding
new copy and pagination for the not found tab.

Link to Trello card

https://trello.com/c/g08YzsRn/224-bulk-search-stress-test-bulk-search-limits

Checklist

  • Attach to Trello card
  • Rebased main
  • Cleaned commit history
  • Tested by running locally

We want the bulk search response to live for as long as someone needs to
access it.

The approach is based on a typical session window where 30 minutes of
inactivity will cause the response to expire.

There is a bug in the implementation at the moment where response
always expires 30 minutes after it was originally created rather than 30
minutes from when it was last accessed.
The GOVUK pagination component doesn't support being rendered in a tab.

I decided to add a new component that wraps the current GOVUK component
but overrides the link rendering to include a fragment.

This allows the links to use the current tab as part of the URL and
navigate the pagination without affecting the tab value.
We want to set expectations around the upload limits.
@richardpattinson
Copy link
Contributor

Are there any tests that cover the new pagination case?

@felixclack felixclack merged commit 0b2e195 into main Sep 25, 2024
13 checks passed
@felixclack felixclack deleted the not-found-pagination branch September 25, 2024 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants