Timeline for How to handle pagination logic in a layered architecture without making premature decisions?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 28, 2024 at 14:23 | history | edited | Hadi Satrio | CC BY-SA 4.0 | Fix a typo in the title. |
| Dec 28, 2024 at 14:02 | vote | accept | Hadi Satrio | ||
| Dec 28, 2024 at 9:43 | answer | added | Doc Brown | timeline score: 1 | |
| Dec 27, 2024 at 14:04 | comment | added | Hadi Satrio | I meant to draw some contrast to the typical, non-paginated load scenario in which the application layer would have full control over what should happen when the process fails. | |
| Dec 27, 2024 at 14:02 | comment | added | Hadi Satrio | @DocBrown, in subsequent loads, the presenter would indirectly talk to the entity through Iterator#next hence bypassing the interactor. Perhaps I should have wrote "application" rather than domain, apologies for the confusion. | |
| Dec 27, 2024 at 8:30 | comment | added | Doc Brown | @HadiSatrio: I still I have some trouble to understand the question, especially the "domain may lose control over the flow of events, particularly when errors occur ....". You implement things using iterables and exceptions. In case an error occurs in the data access layer during some iteration, it generates an exception which will bubble up through the intermediate layers, which can ignore it, catch and process it, or catch & process it partially and rethrow it. Where in this scenario does the domain may lose control over the flow of events? | |
| Dec 27, 2024 at 8:17 | comment | added | Doc Brown | @RikD: the typical approach to avoid pagination at the UI level is to provide a filter mechanism to the user which lets them reduce a large list of items (>1000) to a number which is small enough to be handled by scanning visually (<20). Unfortunately, sometimes the data/filter combination returns a number of items like 100~200, from where the user may decide not to fiddle out a better search criteria, but still want to scan visually. Or in other words: pagination can be a valid concern, and this question is definitely worth to be answered. | |
| Dec 27, 2024 at 0:50 | comment | added | Hadi Satrio | Regardless of whether it's a good UI/UX design, I think it's a common enough problem in user-facing applications to be discussed. | |
| Dec 26, 2024 at 21:34 | comment | added | Rik D | 9/10 times (made up statistic) the need for pagination is a sign of bad UI/UX design. Users don’t want to browse several pages to get to the thing they need. Before diving into technical solutions, talk to your users about how you can present the data they need, without displaying it in a paginated list. | |
| Dec 26, 2024 at 16:06 | answer | added | candied_orange | timeline score: 3 | |
| Dec 26, 2024 at 15:35 | history | asked | Hadi Satrio | CC BY-SA 4.0 |