-
Notifications
You must be signed in to change notification settings - Fork 685
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
Feature/scan_force_arg #1010
Feature/scan_force_arg #1010
Conversation
help='Maxmimum number of tracks to scan') | ||
help='Maximum number of tracks to scan') | ||
self.add_argument('--force', | ||
action='store_true',dest='force',default=False, |
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.
Missing spaces after the commas here. Will break flake8 linting when Travis CI gets up to speed again.
All in all, looks simple and good. :-) Either you (change locally and force-push to your branch, and the PR will be updated) or the one merging this should take the time to clean up the commit history to two commits:
|
Added the spaces, shortened the help to your suggestion, and slimmed it down to two commits. |
https://travis-ci.org/mopidy/mopidy/jobs/52370009 is still reporting style issues (one of which I think was even there from before). Get those fixed (and for bonus points update the changelog and docs) and this is ready to merge :-) |
local: Add --force flag to 'mopidy local scan' command
In issue #910 an enhancement was requested to add a
--force
argument to the scan command.Also, while working on #910 I noticed the help text for
--limit
had a miss-spelled word so went ahead and fixed that.