-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
"Unknown argument" error using TypeORM CLI #6896
Comments
Why is that a problem for yarn / npm scripts? Looks like this behavior changes in |
https://github.com/yargs/yargs/blob/master/CHANGELOG.md#-breaking-changes-3
Apparently we're using strict mode which I did not know. |
the CLI command `query` had an implicit `query` positional parameter and in earlier versions of yargs that was okay - but in the later versions aiming for more correct code they've refactored it to not support that explicitly define the `query` positional parameter & add a helpful description so people can tell what it is for fixes typeorm#6896
the CLI command `query` had an implicit `query` positional parameter and in earlier versions of yargs that was okay - but in the later versions aiming for more correct code they've refactored it to not support that explicitly define the `query` positional parameter & add a helpful description so people can tell what it is for fixes typeorm#6896
We call scripts from other scripts and |
the CLI command `query` had an implicit `query` positional parameter and in earlier versions of yargs that was okay - but in the later versions aiming for more correct code they've refactored it to not support that explicitly define the `query` positional parameter & add a helpful description so people can tell what it is for fixes #6896
the CLI command `query` had an implicit `query` positional parameter and in earlier versions of yargs that was okay - but in the later versions aiming for more correct code they've refactored it to not support that explicitly define the `query` positional parameter & add a helpful description so people can tell what it is for fixes typeorm#6896
Issue type:
This used to work until recently:
Now,
--
must be used to avoid this error which is problematic when trying to run this via yarn/npm scripts.[x] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[ ]
mysql
/mariadb
[ ]
oracle
[x]
postgres
[ ]
cockroachdb
[ ]
sqlite
[ ]
sqljs
[ ]
react-native
[ ]
expo
TypeORM version:
[x]
latest
[ ]
@next
[ ]
0.x.x
(or put your version here)Steps to reproduce or a small repository showing the problem:
The text was updated successfully, but these errors were encountered: