-
Notifications
You must be signed in to change notification settings - Fork 272
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
Add no-flags, add short aliases, make aliases more consistent #1748
Conversation
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.
The for loop looks strange in the class body,
it should be possible to just define flags like this, right?
flags = {
**flag(...),
**flag(...),
...
}
Also, there are some boolean flags remaining, that are not setup using flag
, can you transform those as well?
I thought the loop is the most elegant solution because I forgot about |
do we want a --no-progress flag? |
Yes, I think that makes sense. In case we switch the default for example. Having all boolean flags consistent and automatically negated is a big plus I'd say. |
That leads me to another question: the should the |
shortform negation doesn't make sense, correct. How does |
afaik it doesn't. It can't handle short/long tuples, only strings. So I think we need to add a long yes/no flag and the short form we have to build ourselves |
It doesn't. And it also does not make sure that only one of the flags is given. |
What do you mean exactly? When I give |
I somehow expected that traitlets would raise an error for |
Codecov Report
@@ Coverage Diff @@
## master #1748 +/- ##
==========================================
- Coverage 91.62% 91.28% -0.34%
==========================================
Files 185 185
Lines 14382 14380 -2
==========================================
- Hits 13177 13127 -50
- Misses 1205 1253 +48
Continue to review full report at Codecov.
|
Fixes #1738