Lineage events paging update #2577
Merged
+236
−182
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.
Problem
Paging on the Lineage Events Page was pulling all the lineage events for all pages without using an offset.
Closes: #2455
Solution
We want to refresh our paging strategy and aesthetic overall to reflect a canonical set of mechanics as well, so this update includes some other assorted changes including
This change is inspired from some of the work in this ticket. #2455
Thanks https://github.com/ShreyasGit51283 for your work in thinking about how to better solve this problem.
One-line summary:
Refactor of the Lineage Events Page of our Application
Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)