Since the replacement from Mermaid to Stunner in our VSCode plugin for SWF, it has been identified that while changing the text, the diagram viewer may blink, if too many consecutive updates.

Considerations:

• This is not really a bug. The editor has been designed for owning the source of truth, and the lifecycle for the SWF Viewer is different
• It is actually affecting the user experience in a negative way. in case of using the tooling editors (vscode, etc)
• The goal for this task is to improve the performance and result in a smooth user experience by: identifying unnecessary operations, removing/reusing DOM elements as much as possible, and postponing scripting operations 
• As a result from this, the expectation is to fix the bad experience, but further iterations on this lifecycle must be done in the whole tooling architecture, in order to achieve efficient workflow updates. See KOGITO-7198 for more information

Issues:

• UI blinks
• In case of stressing the setContent calls, at some point also some exception at client side appears
• State being lost
  • Mediators: the actual scale/translation viewport levels are being lost accross setContent calls
  • Selection: the actual node selection, if any, is being lost accross setContent calls

Actions:

• Avoid reloading the whole DOM elements on every single setContent call (avoid some DOM manipulations)
• Preverve graph UUIDs when calling setContent multiple times, if possible
• Preserve canvas root UUID
• If workflow id changes, it will reload he whole editor
• Memory checks