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

fix: Use real paths from argvs instead of dummy hard-coded file #65

Merged
merged 1 commit into from
Feb 22, 2017

Conversation

okonet
Copy link
Contributor

@okonet okonet commented Feb 21, 2017

This PR is an ongoing work on #6 which enables to pass the path to webpack config as argument. It will overwrite it if confirmed by the user.

@okonet okonet self-assigned this Feb 21, 2017
Copy link
Member

@TheLarkInn TheLarkInn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we have a fixture already in place that covers this I assume?

@okonet
Copy link
Contributor Author

okonet commented Feb 22, 2017

Covers what?

const dummyConfigLoc = require.resolve(path.join(process.cwd(), 'example/webpack.config.js'));
const outputConfigLoc = path.join(process.cwd(), 'example/neo-webpack.config.js');
require('../lib/migrate.js')(dummyConfigLoc, outputConfigLoc);
const filePaths = argv._;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

._argv is being used in init as well. Perhaps move the var outside the loop and pass the same variable to init too?

@evenstensberg
Copy link
Member

lgtm ✅

  • optional fix left as comment

@okonet okonet merged commit a46edbb into master Feb 22, 2017
@TheLarkInn TheLarkInn deleted the fix/migrate-paths branch February 22, 2017 21:15
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

Successfully merging this pull request may close these issues.

3 participants