Corpus Management - v2 Empty state - Deletion of an item
What does this MR do and why?
This MR resolves #356613 (closed)
Problem:
Corpuses are paginated, and request returns 10 records based on the cursor.
Empty state will appear when we delete last item on any page even when previous pages have corpuses.
Now:
If user deletes last item on page and previous page exists, user will see previous page with corpus list
Describe in detail what your merge request does and why.
Screenshots or screen recordings
before |
---|
New_Corpus_empty_state_delete_480 |
after |
---|
corpus_management |
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
- Go to any project /root/$PROJECT/
- Go to /root/$PROJECT/-/security/configuration
- Scroll to bottom and select Manage Corpuses.
- You will be at /root/$PROJECT/-/security/configuration/corpus_management.
- You need to have at least 11 corpuses, if you don't you should create 11 corpuses.
- Open second page and try to delete single item on second page
- User would expect to see existing corpuses on the previous page
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #356613 (closed)
Edited by Artur Fedorov