parserPreset key in extended configuration not working

[noelebrun]

Hello,

I put a custom parserPreset in my custom config I'm extending.

I think it's coming from there:
https://github.com/marionebl/commitlint/blob/1e049021eb8f7550fa48a6e8cdd0348227273a39/%40commitlint/resolve-extends/src/index.js#L60

You should maybe put the parserPreset on c and not on config since config is overrides in there:
https://github.com/marionebl/commitlint/blob/1e049021eb8f7550fa48a6e8cdd0348227273a39/%40commitlint/resolve-extends/src/index.js#L24

And the old parserPreset entry (the string one) is still there.

What do you think?

Thanks!

[marionebl]

A PR to fix this with an appropriate test case would be very welcome.

[wldcordeiro]

I think this issue is still present. 😦 Tried creating an extendable config for teams with customized issuePrefixes and it just won't work for me. The links referenced above are 404 now though.

Config that doesn't seem to work.

module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'subject-case': [0],
    'references-empty': [2, 'never'],
  },
  parserPreset: {
    parserOpts: {
      issuePrefixes: ['#', '!', '&', 'no-references'], // no-references is a pseudo prefix because we want explicit opt-out of not referencing.
      referenceActions: null,
    },
  },
};

This seems to ignore the fact that I set referenceActions to null to allow people to just list references and it doesn't accept any of my additional prefixes.