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: Fix config parsing issues #1152

Merged
merged 1 commit into from Dec 13, 2017
Merged

Conversation

kumar303
Copy link
Contributor

Fixes #1151

@kumar303 kumar303 requested a review from rpl December 13, 2017 17:25
config: fakePath,
},
}));
// This makes sure that the config object was applied
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This part of the code didn't have test coverage before.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 535c026 on kumar303:config-fix-1151 into 8a8ee94 on mozilla:master.

Copy link
Member

@rpl rpl left a comment

Choose a reason for hiding this comment

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

r+ looks great

@@ -87,6 +87,13 @@ export function applyConfigToArgv({
}

newArgv[option] = configObject[option];

const coerce = options[decamelizedOptName].coerce;
Copy link
Member

Choose a reason for hiding this comment

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

It would be nice to cleanup this method further in a followup (e.g. options[decamelizedOptName] could be assigned to a variable near line 48 and then use it where we are currently using options[decamelizedOptName], only to make the rest of this method a bit more readable).

@rpl rpl merged commit c081a22 into mozilla:master Dec 13, 2017
@kumar303 kumar303 deleted the config-fix-1151 branch December 13, 2017 19:09
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.

None yet

3 participants