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
UIEH-1141: Pagination investigate #1382
Conversation
Test errors found for test. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-eholdings/job/PR-1382/1/ |
yarn run v1.22.5 $ eslint ./ && stylelint "src/**/*.css" |
Test errors found for test. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-eholdings/job/PR-1382/2/ |
yarn run v1.22.5 $ eslint ./ && stylelint "src/**/*.css" |
Test errors found for test. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-eholdings/job/PR-1382/3/ |
UIEH-1141: Investigate : Change results list scrolling behavior
Story
UIEH-1141
Description
Throughout this work, it was revealed
Load more button pagination
This way was implemented for Titles list for package in UIEH-1004 PR.
Here a
<QuerySearchList>
component was created for this implementation. For other package / header / provider implementations, developers will need to change<QueryList>
to<QuerySearchList>
and add epics to get the collection. The PR for UIEH-1004 can be used as a code base.The preliminary estimate of each task to change the pagination will be no more than 3-5 SP.
NextPrev buttons pagination (STCOM-829)
It is easier to implement this based on the previous method. It has the same code with minor changes in the reducer and changes the load more button to
next-prev
buttons. How this can be implemented is described in the code for the current PR.For this way we need one ticket to change
<QuerySearchList>
component withnext-prev
buttons. And estimate it as 2 SP. And other thickets for packages/titles/providers/ lists could be 5 SP.Pagination from STCOM-827
It is difficult to check because this functionality is not merged. But it has a simple implementation (based on the documentation) and our code already has all the necessary details for its implementation. For this way we need story for implementing
<Pagination>
component for<QuerySearchList>
. It could be estimate as 5 SP. And other tickets for lists could be 5 SP too.Focus functionality
It will be working the similar for all of this ways. But it's difficult functionality and we need the separate story for its implementation.