Skip to content
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

Always return originally passed choice for Choice() #1318

Conversation

altendky
Copy link
Contributor

closes #1277
replaces #1278

Copy link
Contributor

@sirosen sirosen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry that this took me so long to circle back to and review. I got pulled into other projects (after we spent good effort discussing this behavior, that feels like a waste).

I think this is the right thing to do. Even after a while away from it, reading it makes sense and is pretty reasonable.

I'd like to merge, but before I do, I had one comment about lower vs casefold. Let me know what you think about that.

click/types.py Show resolved Hide resolved
@sirosen sirosen force-pushed the 1277-altendky-return_exact_from_choice_insensitive branch from 4f76c57 to 89e74e8 Compare September 26, 2019 05:33
@sirosen
Copy link
Contributor

sirosen commented Sep 26, 2019

Just to keep the history a little bit clean, I rebased this before merging. (It's my own fault for taking months to review it.)

@sirosen sirosen merged commit 1a714b3 into pallets:7.x Sep 26, 2019
@altendky altendky deleted the 1277-altendky-return_exact_from_choice_insensitive branch September 26, 2019 11:41
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants