-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Provide altered context to callbacks to hide UNSET values as None
#3137
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
Provide altered context to callbacks to hide UNSET values as None
#3137
Conversation
b1ff8ed to
69f842d
Compare
|
Ok I found a solution to reconcile the 2 issues. It's a bit dirty, but it works without side-effects. |
UNSET values as None
|
Thanks! I can confirm that this fixes the issues I've seen in |
|
The tests look good. |
|
@davidism Can you review this? |
|
@kdeldycke Also add change entry. |
|
A ridiculous fix 😅, but I'm fine with it. Maybe in the next release we can figure out some internal API separate from the external one, rather than this bit of magic. |
Oh yes. A bit ashamed by that. That's why I tried to be very explicit in delimiting that fix. Anyone reaching that implementation will understand that this part needs some refactor.
Oh yes. You initiated that direction by helping me identify private methods in the previous months, with |
…lues as `None` Fix: #3136
69f842d to
437e1e3
Compare
Ah yes, good call. Done. |
|
Also, just for reference, this PR pass all my tricky hacks in Click Extra. 😇 |
Also, the advantage of all that |
PR to fix:
This highlight a side-effect introduced in:
UNSETnormalization #3079default=Trueon feature flags is order-sensitive #3071CC @dotlambda