@cynodia/axiom-runtime 0.8.0-alpha.1 → 0.8.2-alpha.1
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/index.d.ts +1 -1
- package/dist/index.js +1 -1
- package/dist/runtime-types.d.ts +11 -0
- package/dist/runtime-types.js +11 -0
- package/package.json +2 -2
package/dist/index.d.ts
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
export { BROWSER_RENDERER_CAPABILITIES } from './runtime-types.js';
|
|
1
|
+
export { BROWSER_RENDERER_CAPABILITIES, BROWSER_TRIGGER_CAPABILITIES } from './runtime-types.js';
|
|
2
2
|
export * from './dom.js';
|
|
3
3
|
export * from './mutation/values.js';
|
|
4
4
|
export * from './mutation/store.js';
|
package/dist/index.js
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
export { BROWSER_RENDERER_CAPABILITIES } from './runtime-types.js';
|
|
1
|
+
export { BROWSER_RENDERER_CAPABILITIES, BROWSER_TRIGGER_CAPABILITIES } from './runtime-types.js';
|
|
2
2
|
export * from './dom.js';
|
|
3
3
|
export * from './mutation/values.js';
|
|
4
4
|
export * from './mutation/store.js';
|
package/dist/runtime-types.d.ts
CHANGED
|
@@ -66,4 +66,15 @@ export declare const BROWSER_RENDERER_CAPABILITIES: {
|
|
|
66
66
|
readonly target: "browser";
|
|
67
67
|
readonly supportedUiKinds: readonly ["view", "container", "text", "repeat", "field-display", "form", "input", "button", "conditional", "diagnostic", "dialog"];
|
|
68
68
|
};
|
|
69
|
+
/**
|
|
70
|
+
* The trigger kinds the browser runtime executes: none. `runtime.ts` implements no trigger
|
|
71
|
+
* handling at all, so a client-authority trigger of any kind would otherwise validate,
|
|
72
|
+
* compile into `ApplicationIR.triggers`, and silently never fire (spec 8.1 §31-36). Naming
|
|
73
|
+
* the empty set explicitly, rather than leaving trigger capabilities unspecified, is what
|
|
74
|
+
* makes `validateGraph`/`compileToIR` reject such a graph instead of shipping it inert.
|
|
75
|
+
*/
|
|
76
|
+
export declare const BROWSER_TRIGGER_CAPABILITIES: {
|
|
77
|
+
readonly target: "browser";
|
|
78
|
+
readonly supportedTriggerKinds: readonly [];
|
|
79
|
+
};
|
|
69
80
|
//# sourceMappingURL=runtime-types.d.ts.map
|
package/dist/runtime-types.js
CHANGED
|
@@ -22,3 +22,14 @@ export const BROWSER_RENDERER_CAPABILITIES = {
|
|
|
22
22
|
'dialog',
|
|
23
23
|
],
|
|
24
24
|
};
|
|
25
|
+
/**
|
|
26
|
+
* The trigger kinds the browser runtime executes: none. `runtime.ts` implements no trigger
|
|
27
|
+
* handling at all, so a client-authority trigger of any kind would otherwise validate,
|
|
28
|
+
* compile into `ApplicationIR.triggers`, and silently never fire (spec 8.1 §31-36). Naming
|
|
29
|
+
* the empty set explicitly, rather than leaving trigger capabilities unspecified, is what
|
|
30
|
+
* makes `validateGraph`/`compileToIR` reject such a graph instead of shipping it inert.
|
|
31
|
+
*/
|
|
32
|
+
export const BROWSER_TRIGGER_CAPABILITIES = {
|
|
33
|
+
target: 'browser',
|
|
34
|
+
supportedTriggerKinds: [],
|
|
35
|
+
};
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cynodia/axiom-runtime",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.2-alpha.1",
|
|
4
4
|
"description": "Domain-independent runtime that executes an Axiom application graph.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "AskTech AS",
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
}
|
|
32
32
|
},
|
|
33
33
|
"dependencies": {
|
|
34
|
-
"@cynodia/axiom-core": "0.8.
|
|
34
|
+
"@cynodia/axiom-core": "0.8.2-alpha.1"
|
|
35
35
|
},
|
|
36
36
|
"scripts": {
|
|
37
37
|
"build": "tsc -b tsconfig.json tsconfig.test.json",
|