You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.
Pagination needs to be implemented. This issue is especially problematic for users with more than 30 drafts as they are all sorted to the top, which means no published posts are accessible.
This is currently complicated to implement because of offline mode:
How do we handle posts that are cached locally but are not present on the current page of posts fetched? How do we know whether such a post has been deleted or simply pushed onto a later page? What if it's been edited offline?
Also, what about posts beyond the first page that are already cached? When and how will they be updated? Because the current idea is to always fetch the first page of posts on app start / resume, plus any new pages when the user scrolls to the bottom.
@Memphizzz since you've already made extensive predictions and "what ifs" about my present and future time commitments, I can save myself some effort: you're exactly right, I do not have the time to engage when you start off with hostile comments right away.
Pagination needs to be implemented. This issue is especially problematic for users with more than 30 drafts as they are all sorted to the top, which means no published posts are accessible.
This is currently complicated to implement because of offline mode:
Some ideas:
Migrated from vickychijwani/quill#81
The text was updated successfully, but these errors were encountered: