checkdata invalid fields update #147
Merged
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
We were building the whole line all at once, with color based on a single field's value. Now we want to introduce color for other field values, to allow for flagging of invalid fields. Here we make that easier to accomodate by building out the single line string field by field.
|
I don't think there's anything controversial here, so I'll plan to merge soon unless comments come in. Functionality here is helpful in testing simonsobs/socs#87. |
Merged
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.
This adds a feature to the
checkdatascript that will flag invalid field names by displaying them in yellow in the verbose output.For example:
It also contains some changes for dynamically handling the field name column width.