refactor: Remove all old frontend parsing for nested columns #1919
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.
Signed-off-by: Kristen Armes karmes@lyft.com
Summary of Changes
This change removes all the code related to the previous implementation of nested columns that used frontend parsing. This helps to avoid having two unrelated implementations of the same feature.
Things to note:
nestedColumns.isEnabled
config, that has been removed from the default config and config types since it is no longer used, so it should be removed from your configuration as well.Tests
Removed any test that were no longer relevant
Documentation
N/A
CheckList
Make sure you have checked all steps below to ensure a timely review.