[FEAT] Add conventionalCommits.types so its possible to change the default types.

Is your feature request related to a problem? Please describe. Its not necessarily always a node project that uses conventional commits, meaning that its not always possible nor needed to install @commitlint/config-conventional and use commitlint.config.js.

Describe the solution you’d like Just by adding the same pattern used for scopes would fix the issue, meaning that you could add to vscode settings:

conventionalCommits.types = [
    "chore",
    "docs"
]

Describe alternatives you’ve considered Adding @commitlint/config-conventional as global using npm, and creating a “useless” commitlint.config.js file that is inside .gitignore.

[vivaxy]

@yi-Xu-0100 @GustavoFenilli I have a suggestion about the configuration. We can move default types into configuration.

The configuration could supports 3 types of input:

1. For single language:

"conventionalCommits.commitTypes": "conventional-commit-types"

1. For i18n:

"conventionalCommits.commitTypes": "@yi-xu-0100/conventional-commit-types-i18n"

1. For custom types:

"conventionalCommits.commitTypes": [
  {
  	"type": "normal",
    "title": "with title",
    "description": "and description"
  },
  {
    "type": "only-title",
    "title": "only title"
  },
  {
    "type": "only-description",
    "title": "only description"
  },
  {
    "type": "only-type"
  }
]

Other attributes are ignored

It seems straightforward and keep the configuration as simple as possible. What do you think? 😃

[vivaxy]

@yi-Xu-0100

Yes. I agree with your ideas:

1. The default value is "@yi-xu-0100/conventional-commit-types-i18n".
2. The default language is en.
3. The custom configuration overrides all of the default values.

About the reuse of default values:

Is it possible to introduce extends property like eslint config or commitlint config? I’ll try to dig more information about this idea.