editor-style technique about flynt

[koukouchris]

Hello @proteinone,

This is very similar to our approach, when adding editor styles.
We also add a new entry in the build-config.js because this will create a new, separate bundle.

/assets/editor-style.js would look like this:
import './editor-style.scss'

We usually only add global styles and not component specific ones. So that is why you do not necessarily need the import stuff in the editor-style.js.

We add editor styles on /inc/assets.php

add_action('admin_init', function () {
    add_editor_style(Asset::requireUrl('assets/editor-style.css'));
});

We handle all asset loading in inc/assets.php and do not create an extra tinyMce.php, but this is just preference.

The Asset::requireUrl is a helper to resolve the correct path of a given assets.
This most of the time just makes a difference when you run npm run build, then all assets are revisioned, so they get a content hash added to their filename.

Thanks for the feedback! Glad you're enjoying Flynt!

[proteinone]

Thanks @koukouchris !

Great to hear we were on the right path : )

I completely agree about the editor-style.js, we don't need component level styles either.

And the assets.php looks like a better place to enqueue the file also. Good idea.