Add processOldVersions to CCPL to handle deprecated categoryName field #17820
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
biagas
approved these changes
Jun 27, 2022
JustinPrivitera
deleted the
bugfix/JustinPrivitera/2022_06_27/add_processoldversions_to_ccpl
branch
JustinPrivitera
added a commit
that referenced
this pull request
Jun 27, 2022
|
merged w/ develop in #17823 |
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.
Description
Added in processOldVersions for CCPL to handle the deprecated
categoryName.Also added comment to ColorTableAttributes to correct any confusion.
Type of change
[ ] New feature[ ] Documentation update[ ] OtherHow Has This Been Tested?
Added back in the line that sets
categoryNametovolumePlot.py, tested and ran on rztopaz.Also ran w/ CLI and tried getting and setting
categoryNameto test the output messages.Checklist:
[ ] I have updated the release notes.[ ] I have made corresponding changes to the documentation.[ ] I have added tests that prove my fix is effective or that my feature works.[ ] I have added new baselines for any new tests to the repo.