yarramate 1.23.1 → 1.23.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/dist/kind-label.d.ts +21 -0
- package/dist/kind-label.js +20 -0
- package/dist/visual-app/assets/index-CyKofiEE.js +394 -0
- package/dist/visual-app/index.html +1 -1
- package/dist/visual-app-lib/editor.js +27309 -27306
- package/dist/visual-app-lib/types/kind-label.d.ts +21 -0
- package/package.json +1 -1
- package/dist/visual-app/assets/index-5aKNHeZ0.js +0 -394
package/dist/kind-label.d.ts
CHANGED
|
@@ -7,3 +7,24 @@
|
|
|
7
7
|
* before; it is still a lot of bundle for one label.
|
|
8
8
|
*/
|
|
9
9
|
export declare const kindLabelOf: (kind: string) => string;
|
|
10
|
+
/**
|
|
11
|
+
* A kind as a READER should see it on a select or a fact row: the display name
|
|
12
|
+
* the profile authored, then the id the document will actually carry.
|
|
13
|
+
*
|
|
14
|
+
* Both halves, deliberately (Nabeel, 2026-09-05). The properties panel edits
|
|
15
|
+
* the document, so an architect needs the exact token that lands in the YAML;
|
|
16
|
+
* a consultant reading the same panel needs to know what `mule-api` means. The
|
|
17
|
+
* palette can afford the name alone because nothing there is being written.
|
|
18
|
+
*
|
|
19
|
+
* NEVER the value of a select. The value stays the bare label, because that is
|
|
20
|
+
* what the staged operation carries and `apply` refuses a qualified identity as
|
|
21
|
+
* an unknown kind (YM401).
|
|
22
|
+
*
|
|
23
|
+
* Falls back to the label alone where the profile authored no name, which is
|
|
24
|
+
* every core kind, and where it authored one identical to the id, which would
|
|
25
|
+
* otherwise read `dataObject (dataObject)`.
|
|
26
|
+
*/
|
|
27
|
+
export declare const kindOptionText: (option: {
|
|
28
|
+
readonly label: string;
|
|
29
|
+
readonly name?: string;
|
|
30
|
+
}) => string;
|
package/dist/kind-label.js
CHANGED
|
@@ -7,3 +7,23 @@
|
|
|
7
7
|
* before; it is still a lot of bundle for one label.
|
|
8
8
|
*/
|
|
9
9
|
export const kindLabelOf = (kind) => kind.slice(kind.lastIndexOf('#') + 1);
|
|
10
|
+
/**
|
|
11
|
+
* A kind as a READER should see it on a select or a fact row: the display name
|
|
12
|
+
* the profile authored, then the id the document will actually carry.
|
|
13
|
+
*
|
|
14
|
+
* Both halves, deliberately (Nabeel, 2026-09-05). The properties panel edits
|
|
15
|
+
* the document, so an architect needs the exact token that lands in the YAML;
|
|
16
|
+
* a consultant reading the same panel needs to know what `mule-api` means. The
|
|
17
|
+
* palette can afford the name alone because nothing there is being written.
|
|
18
|
+
*
|
|
19
|
+
* NEVER the value of a select. The value stays the bare label, because that is
|
|
20
|
+
* what the staged operation carries and `apply` refuses a qualified identity as
|
|
21
|
+
* an unknown kind (YM401).
|
|
22
|
+
*
|
|
23
|
+
* Falls back to the label alone where the profile authored no name, which is
|
|
24
|
+
* every core kind, and where it authored one identical to the id, which would
|
|
25
|
+
* otherwise read `dataObject (dataObject)`.
|
|
26
|
+
*/
|
|
27
|
+
export const kindOptionText = (option) => option.name === undefined || option.name === option.label
|
|
28
|
+
? option.label
|
|
29
|
+
: `${option.name} (${option.label})`;
|