I'm faced with a similar dilemma. The tools object passed into the constructor requires that the class property be a class/variable reference, not just the name of a class in string form.

tools: {
    header: {
      class: Header,    // <--- must be a defined class at this point
      inlineToolbar : true
    },
    // ...
  }

This makes JSON.stringifying the tools object impossible. I haven't found an elegant way to pass a JSON string from the server to the JavaScript to construct this tools object without manually looping and replacing the class value in each tool definition.

Am I completely missing something? If there was a way to configure tools post-construction, this might be easier, and would solve the issue raised in this thread, too.

It could be implemented, but we need to understand why you prefer changing the tools list rather than just destroy/reinitialize the editor.

I don't know about the others, but from my perspective, reinitialization does not work well UX-wise. Autofocus often reapplies, scroll resets, the editor's content flashes, and in some situations, the layout around the editor will "jump" due to editor size changes. All those things can be prevented somehow, but it's not a pleasant process to debug all those problems and apply fixes.

same issue here. We are updating config of the custom tool depending on the outer state. Unfortunately it does not take any effect...

Hi @neSpecc, any update on this?

I tried a monkey patch in my personal project to add this functionality. Not sure if its right, but works fine.

happy to create a PR with necessary tweaks if you like!