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
Currently a SVG of a BPMN file can only be generated manually trough the VSCode Extension.
It would be nice to externalize this functionality to be available as a automated step during a build pipeline (eg. maven).
So we don't need to first do it manually as developers and also don't need to check in generated code.
Also currently when we don't generate the SVG manually, the SVG endpoint (for example used by the management console) then doesn't/can't give a SVG as response (as of my understanding).
For a simple solution the functionality to generate the SVG from a BPMN file path could be externalized to a own npm package.
This package could then be used in maven via the frontend-maven-plugin.
And afterwards (optionally), it would be nice to have it as a own maven plugin.
The text was updated successfully, but these errors were encountered:
I'm not against having such library, but we actually have plans to have Management Console not depend on the SVG anymore, and instead render a read-only BPMN Editor of the process based on the upcoming new BPMN Editor.
Currently a SVG of a BPMN file can only be generated manually trough the VSCode Extension.
It would be nice to externalize this functionality to be available as a automated step during a build pipeline (eg. maven).
So we don't need to first do it manually as developers and also don't need to check in generated code.
Also currently when we don't generate the SVG manually, the SVG endpoint (for example used by the management console) then doesn't/can't give a SVG as response (as of my understanding).
For a simple solution the functionality to generate the SVG from a BPMN file path could be externalized to a own npm package.
This package could then be used in maven via the frontend-maven-plugin.
And afterwards (optionally), it would be nice to have it as a own maven plugin.
The text was updated successfully, but these errors were encountered: