I wonder should we split html layer to smaller layer packages per template language

I've added it similar to spacemacs

but it adds a lot of packages that may not be useful for users

@dvcrn why we wipe user configuration? Just wondering are there some conflicts or caveats?

I designed it so that 1 version of the .proton file always equals to 1 state of the editor. Proton should be able to reproduce 1 exact state whenever needed When I built sublimious (for sublimetext) I had it that separate settings were messing with the addon and suddenly it wasn’t sure anymore if there was an error with some user setting or with the addon itself

Or stuff like, what if proton wants to set a key but the user set it before in his config? Which one is dominant? How can we know if the user set it before or if it was automatically set

got it, make sense. Thanks.

that’s why I delete packages, deactivate them and kill everything else

I was thinking that if proton needs to change config that was set by user it will be changed according current priority implementation

we change configs inside layers and if user don't like this change he can always add it to his .proton which has the highest priority

just want to figure out if removing is required

we could add a key to deactivate this behaviour but I’m a big fan of the stateless design

if possible I would even delete styles and keybindings but that wasn’t necessary yet

)))

I will try to do more stuff on weekends, currently have limited time(