search

camunda / camunda-modeler-linter-plugin

Check your BPMN diagrams for common issues
37 stars 8 forks source link

Deprecate Plugin #29

Closed philippfromme closed 2 years ago

philippfromme commented 2 years ago

Related to https://github.com/camunda/camunda-modeler-linter-plugin/issues/28

philippfromme commented 2 years ago

There are two ways we could handle compatibility with specific Camunda Modeler versions:

1. Imperative - Plugin is in control

The Camunda Modeler would expose its version and the plugin would check for compatibility. This would involve

2. Declarative - Camunda Modeler is in control

This has been sketched in https://github.com/camunda/camunda-modeler/issues/1043. Plugins would declare their compatibility and the Camunda Modeler would check for compatibility.

@nikku @camunda/modeling-dev Your thoughts?

nikku commented 2 years ago

My proposal is that we await further feedback before doing advanced deprecation action here.

As of now it seems like the existing communication is enough; we do have relevant issues in all repositories, and our built-in debugging steps allow users to root-cause the issue (https://github.com/camunda/camunda-modeler/issues/3234).

I personally like what you sketched https://github.com/camunda/camunda-modeler-linter-plugin/issues/29#issuecomment-1262764353, option :one:.

If you have capacity to pursue this route (create PRs, double check plug-in helper documentation, ...) that would be awesome. Note though that we still miss an "plug-in outdated" notification from within the app for a working end-to-end story.

philippfromme commented 2 years ago

Okay, I'll unassign myself for now.

philippfromme commented 2 years ago

We'll continue with https://github.com/camunda/camunda-modeler/issues/3239.