> It proposes a change to the actions to have a state, which is an optional function that returns an integer to depict the state of each action; 1 for active, 0 for inactive, -1 for disabled.

Thanks for the suggestion, I think it might be a good idea to have this kind of custom check, so go ahead. Remember to add some example [here](https://github.com/artf/grapesjs/blob/7d1dff957d62bbbaefd75b042e4092ae6f28e3d1/src/rich_text_editor/index.js#L138) 


> Also, what do you think about the idea of passing an empty array to actions on the config, not rendering any of the default actions

It would be a breaking change, so I'd like to avoid it.

> I'm creating my own RTE without using CKEditor (as CKEditor has some unusual behaviour with custom components), and in order to not render the bold action first, I pass it in the actions: ['bold'] configuration, but then editor.RichTextEditor.remove('bold'), as I would like have other commands before the bold and this is the only way i could think of doing so

Well, if you're creating a plugin for the built-in RTE and you want to remove all of the initial actions you can do this:
```js
const rte = editor.RichTextEditor;
rte.getAll().forEach(action => rte.remove(action.name))
```

GrapesJS Issues

[QUESTION] `RichTextEditor` update