[request] allow add entry without create a file

[bluelovers]

hope can allow add entry without create a config file

and allow export config

[lppedd]

@bluelovers hi! What do you mean with "add entry"? Do you want to add a new commit type without creating a config file?

[bluelovers]

yes types and scopes

[karfau]

Export would be nice to get started writing an own file. :+1:

[bluelovers]

if can import and update form network link also nice

[lppedd]

I will provide a way to export the default configuration in the project base directory.
Then you'll be able to edit it and set it as custom. I plan on automatically recognizing the custom file too, if it is in the project base directory.

[karfau]

FYI: you might want to consider module root vs project root.

I know that quite some people are working on related modules in a singel project, especially regarding related npm repos, where one module relates to a git(hub) repo. Each of these will most likely have a different set of scopes.

Not sure how much complexity this could add, but at least creating it in a way that doesn't block this way of handling things might be beneficial, if it's possible.

[lppedd]

@karfau Yeah I was thinking about module/project. Currently components are available per project. Also, starting from 2020.* a new "workspace" concept has been introduced, so I'll postpone the module thing for now.

A note: I'd like to maintain plug-ins as simple as possible so to minimize problems

[lppedd]

I've provided a way to export the built-in defaults with #5

[lppedd]

@bluelovers I don't think I will make a complicated UI to add entries.
Do you still want this even if I provided a way to export the default file?