Why did you remove inline style management?

[Dobby85]

Hi 👋

I saw the parameter avoidInlineStyle in the editor configuration have been deprecated because it does not handle responsive and does not have state management.

My question is: Why do you have totally remove it? Why don't you let the final user choose knowing the advantage and disadvantages of each solution?

For example in my case. Every styles is under #id or .class but in a specific block that I use to generate dynamic list of dynamic data, inline style is the only solution. In my dynamic data, I have a field that is used to store text or background color and I wan't to apply it dynamically on each element in my list. In the next image, we see on the right that the color is get from the dynamic list and then apply as the background of each div.

The setStyle component method can already receive an inline option. This option could be used to store the style that we explicitly want as inline in another model property line model.set('inlineStyle', inlineStyleObject) and if it's not explicitly wanted, we keep the current way of working.

The above function is buildFromModel in CssGenerator.ts.

I'm ok to work on it. I prefer ask to know what you think of the idea before I start working on it. In my idea we kept all style management as it is now but we let the possibility to set inline style if it is what we want.

What do you think of that?

Thanks for your return,

[Dobby85]

I just understand how it really works now and that I just have to remove avoidInlineStyle from my config to get evrything like I want...