Expected Behavior
I tried to extend the new @commitlint/config-conventional and add some "overrides" into that one. What I'd expect is that the new parserPreset is also reused, besides the rules.
Current Behavior
Right now if you extend configs like there, the parser preset remains undefined. This is a dump I got from the @commitlint/load package.
{
extends: [ '@commitlint/config-conventional' ],
rules: {
'header-max-length': [ 2, 'always', 80 ],
'type-enum': [ 2, 'always', [Array] ]
},
parserPreset: undefined
}
Affected packages
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
| Executable |
Version |
commitlint --version |
8.3.0 |
git --version |
2.17.1 |
node --version |
12.11.1 |
Expected Behavior
I tried to extend the new
@commitlint/config-conventionaland add some "overrides" into that one. What I'd expect is that the newparserPresetis also reused, besides the rules.Current Behavior
Right now if you extend configs like there, the parser preset remains
undefined. This is a dump I got from the@commitlint/loadpackage.Affected packages
Possible SolutionSteps to Reproduce (for bugs)ContextYour Environment
commitlint --version8.3.0git --version2.17.1node --version12.11.1