diagrams

Commit Graph

Author	SHA1	Message	Date
Phuoc Tran	fa48533af3	add pre-commit to verify commit before create PR (#1066 )	1 year ago
gabriel-tessier	751a05438d	fix(tests): set lower for case sensitive system (#805 )	3 years ago
Marc Bruggmann	90dd23926b	feat: Basic support for C4 model primitives. (#508 ) * Basic support for C4 model primitives. * Use the "rect" shape for nodes With the record shape we used before, graphviz would trip over edges that set constraint=False. * Adopt C4 terminology: Rename Dependency -> Relationship * Adopt C4 terminology: Rename type -> technology * Extract a shared C4Node This makes the code more DRY, but also allows to add company- specific extensions more easily. One need we have is to slightly adapt the terminology. At Spotify, we happen to call `Container` a `Component` for example. This is now easier to implement on top of the shared `C4Node`. * Add "C4" shield to the README * Document how to produce a C4 diagram	3 years ago

Author

SHA1

Message

Date

Phuoc Tran

fa48533af3

add pre-commit to verify commit before create PR (#1066 )

gabriel-tessier

751a05438d

fix(tests): set lower for case sensitive system (#805 )

Marc Bruggmann

90dd23926b

feat: Basic support for C4 model primitives. (#508 )

* Basic support for C4 model primitives.

* Use the "rect" shape for nodes

With the record shape we used before, graphviz would trip over
edges that set constraint=False.

* Adopt C4 terminology: Rename Dependency -> Relationship

* Adopt C4 terminology: Rename type -> technology

* Extract a shared C4Node

This makes the code more DRY, but also allows to add company-
specific extensions more easily. One need we have is to slightly
adapt the terminology. At Spotify, we happen to call `Container`
a `Component` for example. This is now easier to implement on top
of the shared `C4Node`.

* Add "C4" shield to the README

* Document how to produce a C4 diagram

3 Commits (06a9768839848e2f55b68c0eb5bf3d6f39062a09)