One json to rule all configs

[ryuukk]

Problem description

When i write a plugin, i don't want to write 54545454 different files for configs

It bloats the folder structure, it's hard to identify the right file to edit, just let me open one single file and do my edits there

Preferred solution

a single file: my-plugin.sublime

{
    // correspond to: my-plugin.sublime-commands
    "commands": {
    },

    // correspond to: my-plugin.sublime-settings
    "settings": {
    },

    // correspond to: my-plugin.sublime-menu
    "menu": {
    },

    // etc..
}

Alternatives

Can't think of an alternative

Additional Information

No response

[giampaolo]

The advantage of multiple files though, is that you can override them individually. E.g. from my User/ package I may want to override another package's menus, commands displayed in the palette, etc.

[ryuukk]

this is irrelevant, this behavior you describe will still exist, it's just a json key to override

besides, the use case here is for personal plugins, i have 0 desire to manage billions of small json files, my personal experience shouldn't suffer