[feature request] Make custom tokens configuration file more descriptive

Hi! At first, thanks for the plugin! It looks really promising.

The current approach for storing custom tokens configuration, i.e. cc_defaults.json, seems not enough self-descriptive. E.g. in case this file is put into VCS with a project it might get confusing for other people who not have the plugin installed. There is no hint what this file is for or any explicit reference to the plugin.

It might be helpful to create additional field in the JSON schema for such purposes, e.g. above the current “types” root field. Or consider using a different format for this file, e.g. YAML which supports comments. Another helpful thing might be allowing to use different name than cc_defaults.json, now it doesn’t work for any other name - “The file is not valid” popup appears.

[gcwiak]

👍 I like the idea with auto-detecting, worked like a charm when I added the file to another project. And it makes the configuration even simpler. I’m happy with closing the issue, thank you for doing the improvement! 😃

[gcwiak]

Thanks a lot! Ability for custom naming is really helpful.