You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from 1.1.25, the supportsEditor(), supportsView(), and supportsSelection() methods are no longer called. The DiagramTextIntentProvider gets the text from the DiagramTextProvider without checking these methods first. That means that a DiagramTextProvider implementation could provide bogus diagram text that is not suitable for the current selection.
Another side effect is that the diagram gets overwritten when focus switches to the PlantUML view. This makes navigating that view almost impossible.
I can reliably reproduce this issue with Eclipse Capra when switching from 1.1.24 to 1.1.25 or 1.1.26, so I'd consider this a regression.
The text was updated successfully, but these errors were encountered:
steghoja
pushed a commit
to steghoja/plantuml
that referenced
this issue
Sep 27, 2021
This patch introduces a change to the DiagramTextIntentProvider to
check if the DiagramTextProvider supports the current view and
selection. This makes sure that only DiagramTextProviders that should
contribute a diagram do so.
Starting from 1.1.25, the
supportsEditor()
,supportsView()
, andsupportsSelection()
methods are no longer called. TheDiagramTextIntentProvider
gets the text from theDiagramTextProvider
without checking these methods first. That means that aDiagramTextProvider
implementation could provide bogus diagram text that is not suitable for the current selection.Another side effect is that the diagram gets overwritten when focus switches to the PlantUML view. This makes navigating that view almost impossible.
I can reliably reproduce this issue with Eclipse Capra when switching from 1.1.24 to 1.1.25 or 1.1.26, so I'd consider this a regression.
The text was updated successfully, but these errors were encountered: