-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Deprecating Choices.default #139
Conversation
And I guess the caveat is that if it is there for a reason that's not immediately apparent, should it be doing something? |
Jeez, whoever wrote this really should have written some documentation... (checks blame log)... oh :-) I think your analysis is correct - this is an artefact of the change introduced by #33. With that behavior change, The two things to check for confirmation will be the Toga test suite, and the Colosseum test suite; although a bug on the latter isn't necessarily a dealbreaker, as Colosseum hasn't seen a whole lot of development. |
Confirmed that Toga test suite runs fine with the dangling code removed. I tried testing Colosseum, but it neither depends on Travertino nor has quite the same relevant bits in its analagous code, so it's apples and oranges. |
Huh... Colosseum is lagging further behind than I remembered... |
@HalfWhitt just in case it hasn't been mentioned before, if you run |
Thanks @rmartin16. I hadn't done it at first (didn't think about Travertino being a separate repository from Toga), and then after I added it, it wasn't seeing the changenote file since it wasn't part of the newer commit. All sorted now : ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the investigation and fix!
I was poking around and noticed that setting
default
on aChoice
seems to not do anything. It's only ever referenced again when validating, and then only does anything if the value being validated isNone
, but a choice is never asked to validateNone
. Removing this code has no effect on any of the tests.Is this just a remnant from before #33? If so, I can add a deprecation warning, remove its use from Travertino's tests (and add one to check it's deprecated), and also remove it from a handful of choices defined in Toga.
PR Checklist: