You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: min and max evaluate key on an empty-input default #237
As per the signature, this is not a bug. default: T must be compatible with the key: (T) -> bool. In your example, None is not a valid input for ({"priority": T'}) -> T'.
I do grant that the behaviour is a) not consistent with builtin max/min and b) needlessly restrictive. If you want to make the behaviour change, please adjust the function definitions accordingly.
Activity
maxfischer2781 commentedon Oct 19, 2026
As per the signature, this is not a bug.
default: Tmust be compatible with thekey: (T) -> bool. In your example,Noneis not a valid input for({"priority": T'}) -> T'.I do grant that the behaviour is a) not consistent with builtin
max/minand b) needlessly restrictive. If you want to make the behaviour change, please adjust the function definitions accordingly.