Add per-command sequence diagrams for hery#7
Open
jnbdz wants to merge 11 commits into
Open
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.
Adds the C4 dynamics level for hery: one sequence diagram per subcommand (entity dispatch, entity init/get/list/valid, query, compose, settings), embedded with prose on a new "hery Commands" page. Participants reuse the C3 component names so the diagrams zoom into the existing architecture view.
Spec-vs-code corrections applied while drawing (diagrams follow the code):
hery entity getwrites only the on-disk entity cache, never SQLite.entitiestable;hery queryonly reads it.hery settingsreadsenv/types.gofrom the cwd, so it fails outside the source tree.valid; the diagram file keeps thevalidatebasename.entity/schema/is constructed but never invoked at runtime, so it appears in no diagram.