You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to extend the new @commitlint/config-conventional and add some "overrides" into that one. What I'd expect is that the newparserPreset 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.
It looks like the tests aren't covering the exact use case of the new conventional changelog parser. I'll take a look tonight to see where the test case is behaving differently. For now, I see that in the tests it's receiving a Promise where the real-world use case is receiving a Function (and thus is not picked up by the // Await parser-preset if applicable-code.
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 newparserPreset
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.Affected packages
Possible SolutionSteps to Reproduce (for bugs)ContextYour Environment
commitlint --version
8.3.0
git --version
2.17.1
node --version
12.11.1
The text was updated successfully, but these errors were encountered: