-
-
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
flag_value converted to str in Click 8 #1886
Comments
The default type of parameters is |
@davidism OK, but in my actual use case, the |
Then it should use |
I think what's affecting this is that we now apply type casting consistently to any value coming through the pipeline. I wonder if setting the type to unprocessed automatically for flag values is safe. |
@davidism Using |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Which is a callable, not a literal value. |
A callable is dynamic... |
This comment has been minimized.
This comment has been minimized.
@crashfrog sorry, it sounds like we're having trouble explaining the difference. You're going to have to trust us that there is, in fact, a difference, this tangent is derailing this issue. |
Consider the following code:
Under click 7, passing the
--answer
option to this script prints42
(an int), as expected. Under click 8, it prints'42'
(a str).Environment:
The text was updated successfully, but these errors were encountered: