[MGNLRESTUI-4] Paging fails when you scroll far down Created: 04/Nov/19  Updated: 24/Jan/20  Resolved: 16/Dec/19

Status: Closed
Project: Magnolia REST Client UI
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Jorge Franco
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Declarative REST clients
Sprint: Declarative REST 12
Story Points: 3

 Description   

If you scroll down about a third of the way down the list in the "Bitbucket (Paging)" demo app, then the list is empty and the black loading bar flashes forever.

The UI should either load the items correctly, or provide a clear limitation - for example only loading a maximum of 500 items, and then showing a message that it won't load more.

 

To reproduce:

 



 Comments   
Comment by Simon Lutz [ 12/Nov/19 ]

Data provider in Vaadin needs to know the size of the result set, but most services do not actually provide it.

jsimak - please add your comment related to the library, thanks!

Comment by Christopher Zimmermann [ 19/Nov/19 ]

What about setting a default page size in case the service does not provide it? Say 500 entries.

Comment by Christopher Zimmermann [ 19/Nov/19 ]

Something that would fulfill the most common needs - but that prevents strange errors.

Comment by Christopher Zimmermann [ 11/Dec/19 ]

Can you clarify "you have to define where in the response you get total size and results per page, is mandatory"? Maybe with an example? Not sure what it means.

Otherwise, what if the endpoint has 2000 records and I scroll to the middle, will the system load 1000 records in memory, or does it load them and 'throw' them away as it approaches the target item? Can it handle that?

Would the viritingrid handle that any different or better?

In general its hard for me to make any kind of recommendation on this, I dont understand the tech - but if the viritin grid is how the problem is solved in other parts of Magnolia (with JCR i guess?), or solves the problem better, I think it would be nice to pursue that solution directly if its not too much work (3SP) rather then having a "half way" solution.

Generated at Mon Feb 12 06:50:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.