@uns-kit/core 2.0.38 → 2.0.39
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 +3 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -76,11 +76,10 @@ console.log(values);
|
|
|
76
76
|
|
|
77
77
|
## Validity / Liveliness
|
|
78
78
|
|
|
79
|
-
UNS attributes can declare how the controller decides whether they are live or stale
|
|
79
|
+
UNS attributes can declare how the controller decides whether they are live or stale; in most apps this is primarily used to drive UI liveliness/activity indicators. In app-level modeling we use two modes only:
|
|
80
80
|
|
|
81
|
-
- `
|
|
82
|
-
- `
|
|
83
|
-
- `lifecycleEndValue`: required for `"lifecycle"` mode (end-state marker, e.g. `"EXITED"`)
|
|
81
|
+
- `interval`: continuously refreshed values (stale after ~2× `expectedIntervalMs`)
|
|
82
|
+
- `lifecycle`: event-driven activity that stays active until a defined end value (`lifecycleEndValue`)
|
|
84
83
|
|
|
85
84
|
```ts
|
|
86
85
|
await proxy.publishMqttMessage({
|