This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
refactor: OPTIC-429: Remove unused FF ff_front_dev_1470_dm_pagination_010422_short #305
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.
Important Note
To read this PR, please go through it commit by commit.
Due to the renaming of files that are identical to old file names, GitHub will show them as internal file modifications. However, if you view it commit by commit, you will discern that it's merely file renaming.
This refer to files in src/components/MainView/GridView/ folder
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
we currently have alot of duplicate code in DM related to pagination on Table/TableOld. no one uses the FF ff_front_dev_1470_dm_pagination_010422_short
Please note, we are maintaining the old behavior.
What does this fix?
Clean code
What is the new behavior?
No changes
What is the current behavior?
No changes
What libraries were added/updated?
No changes
Does this change affect performance?
No changes
Does this change affect security?
No changes
Does this PR introduce a breaking change?
(check only one)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)