-
Notifications
You must be signed in to change notification settings - Fork 0
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
delete specified holdings and any empty clusters that result #153
Conversation
I think it would benefit from some documentation to indicate how to use this. |
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.
OptionParser might clean this up a little bit, but not strictly necessary.
It could use some additional inline documentation, and a mention in the README.
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.
I think it would make sense to at least split out option parsing from the actual deletion (e.g. HoldingsDeleter
should get a pre-parsed set of criteria).
While I agree OptionParser
would simplify this I don't know if we need to do it right now if this works -- eventually I think we should consider a common CLI front-end for all our various scripts (thor is the most popular, but there are a couple other options e.g. gli)
7fba386
to
652a3e4
Compare
Replaced homemade option parsing with optparse and squashed commits. |
No description provided.