Open BeritJanssen opened 6 months ago
NB when it comes to #1340, I wonder how to deal with the fact that some visualizations start tasks, and other don't?
Short answer is that it's one of the things we'll have to figure out if we implement that.
I guess we'll either make that a configuration of the plugin (and part of the metadata sent to the frontend) or say that plugin visualisations are always run as tasks because the main application doesn't know how long they'll take.
As a follow-up of #1387 : to make the visualization components agnostic of the underlying requests to the backend, we might factor out some of the logic involved in getting task ids and polling to the
visualization.service
.