[MGNLRESTUI-13] Improve speed in paginated UI component Created: 16/Dec/19 Updated: 28/Jun/22 |
|
| Status: | Accepted |
| Project: | Magnolia REST Client UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jorge Franco | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Epic Link: | RestClient Maintenance | ||||||||
| Description |
|
When the size of the page in API is small, like 10, the current paginated ui component needs almost 200 elements when you make a big scroll. So, we make 20 calls to show the data. It can takes too much time. We can try reduce the number of elements needed to show after a big scroll, actually 200, to a small number when size of page is so small. |