Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make the "--force" a real flag that does not require anything after it. Fix #690
The old code:
make the
sequelize ... --force
useless becauseargs.force
is a''
which yields!args.force
to betrue
. And the system will ask the user to add--force
again. That's what I encountered in #690.In a nutshell, we need to add something after the
--force
to make it work in this old situation.Now it is:
so when the user adds
--force
, theargs.force
is notundefined
, so everything is OK.Test
I compiled it and run
npm test
and it passed.