Auto-detect type=UNPROCESSED when flag_value has non-basic types#3363
Merged
Rowlando13 merged 3 commits intopallets:mainfrom Apr 29, 2026
Merged
Conversation
kdeldycke
force-pushed
the
flag-value-unprocessed-auto-detect
branch
from
758d9be to
4e4c7a6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This closes #2012 by addressing the left-over cases that were not fixed in #3030.
With this PR, when
flag_valueis not a basic Python type, like a class or anEnumvalue, we do not force the stringification imposed byconvert_type. But still use the later for detection of the guessed type.This way we can preserves programmer-provided Python objects as-is, without requiring having
type=click.UNPROCESSEDsets explicitly, restoring pre-8.0.0 user-friendlyness and user expectations.