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(options): fix losing parserOpts without preset #116

Conversation

nmalaguti
Copy link
Contributor

preset.parserOpts may be undefined if no preset was specified in the
options. _.assign() will return undefined if the first argument is
undefined.

@stevemao
Copy link
Member

You need to provide tests to prove that this is actually fixing something :)

@nmalaguti nmalaguti force-pushed the feature/parserOpts-undefined branch 2 times, most recently from 5ec6486 to 53a18bc Compare October 19, 2015 22:42
`preset.parserOpts` may be undefined if no preset was specified in the
options. `_.assign()` will return `undefined` if the first argument is
`undefined`.
@nmalaguti
Copy link
Contributor Author

Test written :).


it('should pass `parserOpts` to conventional-commits-parser', function(done) {
writeFileSync('test9', '');
shell.exec('git add --all && git commit -m"test9" -m"Release note: super release!"');
Copy link
Member

Choose a reason for hiding this comment

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

remove -m"test9"

@stevemao
Copy link
Member

Thanks. Merging. :)

@stevemao stevemao closed this in e6a9cf3 Oct 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants