Repository navigation
feat: workflow and lifecycle diagrams - #17
Merged
Merged
Conversation
Merged
Contributor
|
🎉 This PR is included in version 0.1.0-rc.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 0.1.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
1 participant
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.
First of three PRs to make stackmap cover every example in the archify gallery. This one covers the three workflows and two lifecycles, and brings the architecture and dataflow examples closer.
Diagrams
kind: "workflow"and"lifecycle"draw as swimlanes. Nodes sit inlanes, and stackmap picks the columns from the edges: the agent still never gives coordinates, where archify makes it write lane, column and pixel positions.phaseslabel column spans. In architecture and dataflow diagrams they are ordered stages, laid out with ELK partitioning.tone(main, security, error) andkind: "return"; grouptone: "security";noteslisted in the inspector.density: "compact"for architecture and dataflow.Layout. Lanes get their own column assignment (in core, shared with validation) and an orthogonal A* router in
packages/layout:Validation. New kind rules: lanes, state types, compact-card sections, phase members and order (including through unphased steps), lane groups that would frame other steps, and a 200-node cap for lane kinds.
Docs. The skill, authoring contract and examples cover the new kinds.
Reviewed in a fresh context. The Critical (a phase loop through an unphased node made the column fixpoint diverge) and all Important findings are fixed, with regression tests.