Paginationforblueprints #137
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pagination for blueprints and Deployments:
For Blueprints:
Get call triggered by users scroll activity
Search based on data fetched so far
Handling of bad network connection by giving retry option for swipe refresh as well as scrolling activity
For Deployments:
Same as above except
Needs error handling and addition of dedicated footer for showing the progress bar while loading.
Currently progress bar appears on top of the list at the bottom.
Open discussion: Should search work on all the data existing on server (without pagination) or on the fetched data by the app (Pagination).