-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
fix: regression with migrate command #1423
Conversation
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.
Need test(s)
@jamesgeorge007 Thanks for your update. I labeled the Pull Request so reviewers will review it again. @evilebottnawi Please review the new changes. |
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.
It is change webpack.config.js
content after tests?
a3093bd
to
d4a919f
Compare
That would require us to bypass the prompts for the entire process to complete. As of now, we're checking against the very first user prompt. |
We should do it, because other steps can be broken too |
7fdc5cd
to
ddb7622
Compare
03f6382
to
4447368
Compare
4447368
to
3786f5b
Compare
What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
The
migrate
command expects a source config file to be passed in as an argument. And for the output, we can either have it as another file or overwrite the source. Added test cases covering these scenarios.If relevant, did you update the documentation?
N/A
Summary
closes #1422
Does this PR introduce a breaking change?
Nope
Other information
N/A