Skip to content
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

--apply should function anywhere in the command #110

Open
RyanMilligan opened this issue Jun 25, 2018 · 0 comments
Open

--apply should function anywhere in the command #110

RyanMilligan opened this issue Jun 25, 2018 · 0 comments

Comments

@RyanMilligan
Copy link

RyanMilligan commented Jun 25, 2018

If I put --apply before the file glob, I get the following output:

> can-migrate --apply **/*.js

  Codemods to simplify upgrading CanJS.

  Usage
  $ can-migrate [<file|glob> ...]

  Updates files according to the CanJS 3.0 or CanJS 4.0 migration paths (minimal, modern, future)
  More info for v3.0: http://canjs.github.io/canjs/doc/migrate-3.html#Modernizedmigrationpath
  More info for v4.0: http://canjs.github.io/canjs/doc/migrate-4.html

  Options
  --apply     -a    Apply transforms (instead of a dry run)
  --force           Apply transforms regardless of git status
  --silent    -s    Silence output
  --config    -c    Path to custom config file
  --transform -t    specify a transform
  --can-version     specify CanJS version to upgrade to

  Examples
  can-migrate **/*.js
  can-migrate --apply **/*.js
  can-migrate -iad **/*.js
  can-migrate **/*.* --transform can-route/register.js
  can-migrate **/*.* --can-version 4

Putting --apply at the end of the command works around this issue. Either --apply should work in the way the help output describes, or the output should be updated to correctly reflect the requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant