@diagc/cli 1.1.7 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -31,6 +31,9 @@ Two groups are distinguished, because the obligations differ:
31
31
  | [marked](https://marked.js.org) | 18.0.6 | MIT |
32
32
  | [@fontsource/kalam](https://fontsource.org) | 5.3.0 | OFL-1.1 |
33
33
  | [@fontsource/caveat](https://fontsource.org) | 5.3.0 | OFL-1.1 |
34
+ | [@fontsource/inter](https://fontsource.org) | 5.3.0 | OFL-1.1 |
35
+ | [@fontsource/jetbrains-mono](https://fontsource.org) | 5.3.0 | OFL-1.1 |
36
+ | [@fontsource/chakra-petch](https://fontsource.org) | 5.3.0 | OFL-1.1 |
34
37
 
35
38
  ### elkjs — election of the GPL branch
36
39
 
@@ -110,9 +113,14 @@ The bundled fonts remain under the OFL and are **not** relicensed by this projec
110
113
  - **Kalam** — Copyright (c) 2014 Indian Type Foundry (info@indiantypefoundry.com)
111
114
  - **Caveat** — Copyright 2014 The Caveat Project Authors
112
115
  (https://github.com/googlefonts/caveat)
113
-
114
- Both are packaged by [Fontsource](https://fontsource.org). The full OFL-1.1 text ships
115
- with each package (`node_modules/@fontsource/{kalam,caveat}/LICENSE`) and is available
116
+ - **Inter** — Copyright 2016 The Inter Project Authors (https://github.com/rsms/inter)
117
+ - **JetBrains Mono** — Copyright 2020 The JetBrains Mono Project Authors
118
+ (https://github.com/JetBrains/JetBrainsMono)
119
+ - **Chakra Petch** — Copyright 2018 The Chakra Petch Project Authors
120
+ (https://github.com/m4rc1e/Chakra-Petch)
121
+
122
+ All are packaged by [Fontsource](https://fontsource.org). The full OFL-1.1 text ships
123
+ with each package (`node_modules/@fontsource/<name>/LICENSE`) and is available
116
124
  at <https://openfontlicense.org>.
117
125
 
118
126
  Under the OFL these fonts may be bundled and redistributed with software, but may not
@@ -8,7 +8,7 @@ This guide is for diagc {{version}}.
8
8
 
9
9
  1. Write or edit `.diagrams/src/<name>.diagram.ts`. A folder is allowed: `.diagrams/src/team/app.diagram.ts` is the diagram `team/app`.
10
10
  2. Run `diagc lint --json`. It prints `[]` and exits 0 when everything is clean. Otherwise each finding has `file`, `severity`, `code` and `message`: fix it and run again. An `error` means the diagram does not compile. A `warning` compiles but is probably a mistake, such as a misspelled type.
11
- 3. Run `diagc publish <name>` and look at `.diagrams/static/<name>.png` to check the picture. It needs Chrome; set `CHROME_PATH` when none is found. The PNG shows the first plane with every group opened and only the layers that plane turns on; other planes and layers are on the page `.diagrams/html/<name>.html`.
11
+ 3. Run `diagc publish <name>` and look at `.diagrams/static/<name>.png` to check the picture. It needs Chrome; set `CHROME_PATH` when none is found. The PNG shows the first plane with every group opened and only the layers that plane turns on; each further plane gets `.diagrams/static/<name>.<plane>.png`, and the other layers are on the page `.diagrams/html/<name>.html`.
12
12
 
13
13
  A person runs `diagc studio` to browse every diagram and to move boxes by hand.
14
14
 
@@ -34,7 +34,7 @@ More node options:
34
34
  | `metadata` | Free-form key and value data. |
35
35
  | `plane`, `layer` | Show the node in one plane only, or put it on a layer. |
36
36
 
37
- More relation options: `layer`, `description`, `id`.
37
+ More relation options: `layer`, `plane` (drawn on that plane only), `description`, `id`.
38
38
 
39
39
  ## Types and kinds
40
40