Repository navigation
Export renderable BPMN diagrams with portable layout - #276
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Catalog and agent-starter BPMN exports described process semantics without diagram geometry, leaving external modelers unable to display the map directly. Both exporters now use a shared deterministic BPMN Diagram Interchange layout with activity bounds, label bounds and edge waypoints, including branches, back edges, self-loops and unresolved manual-review paths. Process IDs, revision/hash documentation, rules and non-executable semantics remain intact.
REA 6.7.0 inspected the public bpmn-js 18.31.0 importer/renderer to identify the interoperability requirement; no reference implementation code or artwork was copied. An actual external modeler in Chromium imports every node/edge, exports SVG/XML and imports the XML again without warnings. The toolkit is a test-only dependency.
Validation: 2,013 Python tests passed (1 skipped); focused exporter/model tests passed; external modeler round trips passed; architecture and whitespace checks passed. CI includes the external-modeler acceptance. This supplies an initial editable layout, not optimized routing or BPMN execution/business-policy certification.