@rse/gradia 1.2.0 → 1.2.2
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.
- package/README.md +17 -4
- package/dst/gradia-api-render-node.d.ts +1 -0
- package/dst/gradia-api-render-node.js +8 -1
- package/dst/gradia-api-type-graph.js +110 -55
- package/dst/gradia-api-type-grid.js +6 -3
- package/dst/gradia-api.umd.js +2 -2
- package/dst/gradia-mcp.js +13 -3
- package/package.json +1 -1
package/dst/gradia-mcp.js
CHANGED
|
@@ -128,8 +128,8 @@ as <name>, terminals as "...", optional parts as [ ... ], repeatable parts as
|
|
|
128
128
|
following node, i.e., the chain is equivalent to "a --> b" and "b --> c".
|
|
129
129
|
- The <edge-name> is rendered as the label of the edge and the <edge-arity> as
|
|
130
130
|
its cardinality label.
|
|
131
|
-
-
|
|
132
|
-
displayed as a regular "<key>: <val>" line:
|
|
131
|
+
- Seven attribute keys are reserved and consumed by the renderer instead of
|
|
132
|
+
being displayed as a regular "<key>: <val>" line:
|
|
133
133
|
- "url: <url>" renders the node box as a hyperlink. Only relative URLs and
|
|
134
134
|
the schemes "http", "https", and "mailto" are honored; any other URL is
|
|
135
135
|
silently dropped and the node box then simply stays unlinked,
|
|
@@ -142,7 +142,17 @@ as <name>, terminals as "...", optional parts as [ ... ], repeatable parts as
|
|
|
142
142
|
is implicitly declared if never referenced otherwise),
|
|
143
143
|
- "container: <type>" marks the node as a container whose members are laid
|
|
144
144
|
out with the diagram type <type> ("graph", "hub", or "grid"), even if it
|
|
145
|
-
has no members at all
|
|
145
|
+
has no members at all,
|
|
146
|
+
- "order: <number>" places the node explicitly (see below).
|
|
147
|
+
- A "graph" (a "graph" container level, too) with at least one node carrying an
|
|
148
|
+
"order" attribute is laid out in that explicit order instead of by the layered
|
|
149
|
+
algorithm: the distinct order values become the rows, top-down in ascending
|
|
150
|
+
order, the nodes of one value fill their row left-to-right in declaration
|
|
151
|
+
order (wrapped into further rows beyond "graph-columns-max" nodes), and the
|
|
152
|
+
nodes without an order follow in the trailing rows. A "grid" places its tiles
|
|
153
|
+
in the order of the attribute, too, the tiles without one trailing. Use it to
|
|
154
|
+
impose a reading order (e.g. the order of a document), which lets every
|
|
155
|
+
reference to an earlier item point upward or leftward.
|
|
146
156
|
- A node cannot be a member of more than one group. As soon as at least one node
|
|
147
157
|
carries a "group" attribute, all nodes without one implicitly belong to the
|
|
148
158
|
group "default", and every edge has to stay within a single group. A nested
|
package/package.json
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"description": "Object Graph Diagram Rendering",
|
|
4
4
|
"keywords": [ "object", "graph", "diagram", "rendering", "svg", "layout", "api", "cli" ],
|
|
5
5
|
"publishConfig": { "access": "public" },
|
|
6
|
-
"version": "1.2.
|
|
6
|
+
"version": "1.2.2",
|
|
7
7
|
"license": "MIT",
|
|
8
8
|
"author": {
|
|
9
9
|
"name": "Dr. Ralf S. Engelschall",
|