Skip to content

Use correct sync, async and reply arrows in sequence diagrams - #217

Merged
markbac merged 1 commit into
mainfrom
claude/project-thread-5v7rv6
Nov 5, 2026
Merged

markbac merged 1 commit into
mainfrom
claude/project-thread-5v7rv6

Conversation

@markbac

@markbac markbac commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Requested by Mark · project thread

Summary

Checked every Mermaid sequence diagram in the repo against UML arrow meaning: ->> is a synchronous call, -->> a reply, -) an async message with no reply.

  • docs/gallery/02_mermaid.md: N->>G: Reading (CoAP NON) becomes N-)G (CoAP NON is fire-and-forget), and G->>B: PUBLISH ... becomes G-)B (no PUBACK is shown). Both the source listing and the rendered copy are updated.
  • examples/poster/release.md: Running 2.1 and Update failed, still 2.0 answer the broker's offer, so they become -->> replies.

The other diagrams (VS Code sample, landscape poster, deck slides, design guide, writing guides) already use the arrows correctly and are unchanged.


Generated by Claude Code

CoAP NON readings and MQTT PUBLISH with no PUBACK are fire-and-forget,
so they use the async arrow (-)). The node's update result answers the
broker's offer, so it uses the dashed reply arrow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WHtcxcAiXX6q2Vy7Htviwg
@markbac markbac self-assigned this Nov 3, 2026
@markbac
markbac merged commit 7accd08 into main Nov 5, 2026
6 checks passed
@markbac
markbac deleted the claude/project-thread-5v7rv6 branch November 5, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants