Commitlint: Support configuring parserOpts (conventional-commits-parser)

[imrekq]

Is it possible?

[marionebl]

Sure. This was part of the functionality up to version 3.
I removed it because nobody ever used it.

What is the use case you have in mind?

[imrekq]

I would like to be able to change the headerPattern and other.

[marionebl]

Can you describe what you want do in more detail? I'm not quite clear what kind of behaviour you want to achieve.

[imrekq]

https://github.com/marionebl/commitlint/blob/70b8278a39e7b4965f6afbaca6db20367375965a/%40commitlint/core/src/library/parse.js#L14

It would be desirable at a level commitlint.config.js to change parseOps

[marionebl]

Sure, I meant more in terms of what commit messages you want to parse.

[imrekq]

We already use conventional-changelog on project with follows params (legacy):

headerPattern: /^(\w*)\(([^\)]*)\)\-(\d+\s.*)$/,
headerCorrespondence: [
    'type',
    'scope',
    'subject'
],

fix(scope)-number_task subject
Now we want to add linter of commits and that he fits pattern...

[marionebl]

I'd opt for boiling this down to a parser-preset support - that would allow changing the loaded preset from conventional-changelog-angular to e.g.@imrekb/imrekbs-convention by passing it to the cli or specifying it via commitlint.config.js. Can you help out on this?

[imrekq]

I am thinking - yes.

[imrekq]

How soon will be release?

[marionebl]

I'll add some docs this evening and release it then. Stay tuned.

[marionebl]

Published with some adaption as 3.2.
Changes

• --parser-preset instead of --parserPreset
• top level parserPreset takes precedence over presets from extended configuration

[imrekq]

Thank you!