-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add --warn-error-options #6520
Add --warn-error-options #6520
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
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.
quick first pass at the quick first pass
25c4f55
to
9ed8555
Compare
@stu-k - A couple big files were deleted by the API doc generation bot ( |
@MichelleArk All the workflow does if it detects changes is run |
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.
Very nice. Did those files get deleted because tSphinx was upgraded?
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.
Tried a bunch of different combinations, all of them looking good!
I did run into a weird issue with yaml loading when warn_error_options
is defined in UserConfig
(profiles.yml
)
for flag in group: | ||
flag_set_by_user = not _flag_value_from_default(flag, args, user_config) | ||
if flag_set_by_user and set_flag: | ||
raise ValueError(f"{flag.lower()}: not allowed with argument {set_flag.lower()}") |
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.
This could be nicer, in cases where I've set warn_error
in UserConfig
and I'm also passing the conflicting --warn-error-options
flag on the CLI:
ValueError: warn_error_options: not allowed with argument warn_error
Sounds like it will be easier to handle in the new click
CLI. It serves its purpose for now, and I'm happy with making it nicer in v1.5+
9c67e2d
to
dacaead
Compare
dacaead
to
0c534d3
Compare
Addressed comments, resolved some merge conflicts, and re-tested (with The following all worked as expected 🎩
-> errors
-> does not error! |
@@ -154,7 +154,7 @@ def get_node_selector(self) -> NodeSelector: | |||
|
|||
@abstractmethod | |||
def defer_to_manifest(self, adapter, selected_uids: AbstractSet[str]): | |||
raise NotImplementedException(f"defer_to_manifest not implemented for task {type(self)}") | |||
raise NotImplementedError(f"defer_to_manifest not implemented for task {type(self)}") |
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.
@emmyoop - Noticed this import error via mypy from the latest changes, addressed it here as part of my merge.
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.
thanks. no idea how i missed that.
resolves #6165
Description
Checklist
--warn-error
Mutually exclusive
--warn-error-options
changie new
to create a changelog entry