-
Notifications
You must be signed in to change notification settings - Fork 93
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
Change Choice.shortcut_key
to property with setter
#349
Conversation
40ef821
to
8f4ab05
Compare
@kiancross, I implemented the fix you suggested in #340: #340 (comment). Checking in about whether it is possible to merge this? Thanks! |
@overhacked Please can you update this branch with latest changes from |
8f4ab05
to
c333dec
Compare
Up to date now. I ran lints and tests before pushing; hopefully CI passes 🤞. |
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.
@overhacked Does some logic need to be added for when auto_shortcut
is changed?
Ensures that `Choice.auto_shortcut` is set to `False` whenever `Choice.shortcut_key` is set to a `str` value and vice versa. Add tests for fix. Fixes tmbo#340 Signed-off-by: Ross Williams <[email protected]>
`auto_shortcut` and `shortcut_key` interact in ways that requires logic when setting either, to ensure that they do not conflict. Signed-off-by: Ross Williams <[email protected]>
c333dec
to
a92cea9
Compare
@kiancross, you're right. I added code to handle blanking |
Great, thank you! |
What is the problem that this PR addresses?
Ensures that
Choice.auto_shortcut
is set toFalse
wheneverChoice.shortcut_key
is set to astr
value and vice versaCloses #340
How did you solve it?
Implemented the suggested fix in PR #340 to convert
Choices.shortcut_key
to a property with a setter.Checklist