On Sun, Jan 31, 2021 at 12:54 PM Christoph Läubrich <lae...@laeubi-soft.de> wrote:
> My plan is to check for the ISourceViewerExtension5 then and call > .updateCodeMinings(); > Or is there a better approach? > This is the strategy taken by the error marker code minings, and IIRC by some other 3rd party CodeMining extensions (eg Spring mapping), and probably the strategy we'll use one day when we add debug info as code mining. I'm not aware of a better one at the moment. There are some tickets open about improving this method to allow to specify some "dirty" codemining providers to refresh and avoid further computation (or caching as workaround) by other codeminings providers). -- Mickael Istria Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
