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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement ability to hide warnings in VO table parsing #8715
Implement ability to hide warnings in VO table parsing #8715
Changes from all commits
1e30869
a71f8a9
0f0288e
93818a2
e206ad9
0ed5907
c5dd4f0
e94daba
82283cd
d790ae0
86abb55
ee9701e
51335e6
ffd55f4
13c67cc
2904429
fb3c873
61f9e98
12ecba0
d26a816
c9cf40e
d21679c
ca8462a
c5add16
94826f0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I look at this, I am actually not sure if alias would work if the config type has changed. When
cfgtype
is not provided, as in the case here, it is inferred from the default value. So with this change, its type is now string, where it used to be boolean. That is going to choke the validator when someone has an olderastropy.cfg
with, say,pedantic = True
set. A possible solution is to explicitly state thecfgtype
as'option'
and provide all the 5 possible options (3 new ones and 2 boolean values).References:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason it still doesn't work right if I specify
option
with mixed types, and it always gets converted to a string. But that's ok, we can still be backward compatible by just checking for False and True as strings when usingconf.verify
. I've added handling of this as well as an extensive test of setting the configuration items (both verify and pedantic).