search

livingsocial / bundler-patch

Update your gems conservatively to deal with vulnerable gems or just get more current.
MIT License
65 stars 3 forks source link

Redo the command names #4

Closed chrismo closed 8 years ago

chrismo commented 8 years ago

currently, 

bundle-patch scan
bundle-patch patch
bundle-patch update

First two are security vulnerability related. Third is a general update.

These names aren't necessarily the best, and if going forward we make this a bundler plugin, then would be nice to stick all of those options underneath patch itself. So, here's an issue I can think out loud about it.

Here's all the options on the 3 commands currently:

  -a, --advisory_db_path  Optional custom advisory db path.
  -g, --gems_to_update  Optional list of gems to update, in quotes, space delimited
  -m, --minor_allowed     Upgrade to the latest minor.release version.
  -s, --strict            Do not allow any gem to be upgraded past most recent release (or minor if -m used). Sometimes raises VersionConflict.
chrismo commented 8 years ago

Instead of scan - could go with a --view option? --view-only. -v is typically a verbose switch. -l | --list might be good. -d | --dry-run could go further and show all the updates without actually doing them (I accidentally had that working at an earlier stage).

I'm probably planning to do away with the notion of patch vs update for determining version behavior differences at least ... so, every run could be considered the same: