-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Mark parameter as deprecated #2263
Comments
I'll work on this |
@davidism I just implemented to show the message with |
Hi, @peacock0803sz, what's the status of this issue? You've linked that PR which has to fix the issue, but it's not clear how exactly - I mean the PR is rather about printing the thing out in Is the more appropriate PR maybe already merged? Or it's not created yet? edited: |
Just wanted to share an example of the second use case, the one where an option is being removed. I changed the option line to look like this:
and then added this at the top of the command function:
If click were to add a ``
|
Thanks for this great project!
Perhaps it's just me who feels that it is rather cumbersome mark a single parameter as deprecated (the closet I found was https://stackoverflow.com/a/50402799). Is there perhaps a more official method to mark a single parameter as deprecated?
That would somewhat be similar to #1507.
Possible scenarios:
--name
as option, but now a dev want's to make sure it's the--sur-name
.Perhaps as an example consider:
and I want to rename
--count
to--greetings-count
.However I don't want to remove
--count
instantly, instead when users use--count
prompt a message that they should use the new--greetings-count
. The usage of--count
and--greetings-count
should be forbidden.Thanks.
The text was updated successfully, but these errors were encountered: