[ 
https://issues.apache.org/jira/browse/YETUS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allen Wittenauer updated YETUS-873:
-----------------------------------
    Release Note: 
<!-- markdown -->
Users:

precommit's commands (docker-cleanup, qbt, smart-apply-patch, test-patch) will 
now exit with an error if they are given a double-dashed option that is 
unknown.  Using `--ignore-unknown-options=true` option will return to the 
previous behavior.  Non double-dashed parameters continue to be considered the 
patch location.

This option will be removed in a future release.

Developers:

This patch adds the `delete_parameter` routine.  It should be called to remove 
an option from the variable that is being used to track which parameters have 
been processed.  The internals of this tracking are still very much in flux and 
may change in the future.

  was:
<!-- markdown -->
precommit's commands (docker-cleanup, qbt, smart-apply-patch, test-patch) will 
now exit with an error if they are given a double-dashed option that is 
unknown.  Using `--ignore-unknown-options=true` option will return to the 
previous behavior.  Non double-dashed parameters continue to be considered the 
patch location.

This option will be removed in a future release.


> Error on unprocessed options/parameters
> ---------------------------------------
>
>                 Key: YETUS-873
>                 URL: https://issues.apache.org/jira/browse/YETUS-873
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Precommit
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Given how frequently we've been eliminating some parameters lately as we make 
> things more automatic and/or pushed to be external (e.g., pylintrc vs. CLI 
> options), it is probably a good idea to start getting stricter on what 
> options are being passed on the CLI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to