@things-factory/integration-ui 9.0.1 → 9.0.4

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.
@@ -1,5 +1,19 @@
1
1
  # 状態登録簿 (StateRegister)
2
2
 
3
+ 状態登録簿(state-register)は、**ドメイン内で特定の状態値を永続的に保持したい場合に使用する仕組み**です。
4
+
5
+ - 状態値はパーマネント(永続的)に保存されます。
6
+ - 自動publish用に設定された場合、値が変化すると自動的にpublish(イベント発行)が行われます。
7
+ - サブスクライバー(購読者)は、購読を開始した時点で現在の値を自動的に受け取ります。
8
+
9
+ この機能は主に[シナリオ](../concept/scenario.md)で以下のようなパターンで利用されます:
10
+
11
+ - ドメイン内の任意の値を永続的に保持したい場合に利用します。
12
+ - 状態登録簿への値の書き込み(state-write)や読み取り(state-read)を通じて、シナリオ内で状態値を活用できます。
13
+ - クライアントに値をpublishする場合、publish tagと同じ名前のstate-registerが存在すれば、その値も自動的に更新されます。
14
+
15
+ ---
16
+
3
17
  [状態登録簿(state-register)](../concept/state-register.md)は、特定の意味を持つ状態の値を定義する画面です。
4
18
 
5
19
  - この機能は通常、[シナリオ](../concept/scenario.md)の[state-write](../task/state-write.md)、[state-read](../task/state-read.md)タスクによって使用されます。
@@ -1,5 +1,19 @@
1
1
  # 상태등록부 (StateRegister)
2
2
 
3
+ 상태등록부(state-register)는 **도메인 내에서 어떤 상태값을 영구적으로(퍼머넌트하게) 유지하고 싶을 때 사용하는 구조**입니다.
4
+
5
+ - 상태값은 퍼머넌트하게 저장됩니다.
6
+ - 자동 publish 용으로 설정된 경우, 값이 변경될 때마다 자동으로 publish(이벤트 발행)가 발생합니다.
7
+ - subscriber(구독자)는 구독을 시작하는 시점에 현재값을 자동으로 전달받습니다.
8
+
9
+ 이 기능은 주로 [시나리오](../concept/scenario.md)에서 다음과 같은 패턴으로 활용됩니다:
10
+
11
+ - 도메인 내의 어떤 값을 영구적으로 유지하고자 할 때 사용합니다.
12
+ - 상태등록부에 값을 쓰거나 읽는 작업(state-write, state-read)으로 시나리오 내에서 상태를 활용할 수 있습니다.
13
+ - 클라이언트에 어떤 값을 publish할 때, publish tag와 동일한 이름의 state-register가 있다면 자동으로 값이 업데이트됩니다.
14
+
15
+ ---
16
+
3
17
  [상태등록부(state-register)](../concept/state-register.md)는 특정 의미를 가지는 상태의 값을 정의하는 화면이다.
4
18
 
5
19
  - 이 기능은 보통 [시나리오](../concept/scenario.md)의 [state-write](../task/state-write.md), [state-read](../task/state-read.md) 태스크에 의해서 사용된다.
@@ -1,5 +1,19 @@
1
1
  # StateRegister
2
2
 
3
+ A StateRegister is used when you want to **permanently (persistently) maintain a certain state value within a domain**.
4
+
5
+ - State values are stored permanently.
6
+ - If set for automatic publish, any change in value will automatically trigger a publish (event emission).
7
+ - Subscribers will automatically receive the current value at the moment they start subscribing.
8
+
9
+ This feature is mainly used in [scenarios](../concept/scenario.md) with the following patterns:
10
+
11
+ - Used to persist any value within a domain.
12
+ - You can utilize state values in scenarios by writing to or reading from the state register (state-write, state-read).
13
+ - When publishing a value to a client, if there is a state-register with the same name as the publish tag, it will be automatically updated.
14
+
15
+ ---
16
+
3
17
  [State-register(state-register)](../concept/state-register.md) is a screen that defines values for states with specific meanings.
4
18
 
5
19
  - This function is usually used by tasks in [scenario](../concept/scenario.md) such as [state-write](../task/state-write.md), [state-read](../task/state-read.md).
@@ -1,5 +1,19 @@
1
1
  # Daftar Keadaan (StateRegister)
2
2
 
3
+ Daftar keadaan (state-register) digunakan apabila anda ingin **menyimpan nilai keadaan tertentu secara kekal (permanen) dalam domain**.
4
+
5
+ - Nilai keadaan disimpan secara kekal.
6
+ - Jika ditetapkan untuk penerbitan automatik, sebarang perubahan nilai akan mencetuskan penerbitan (penghantaran acara) secara automatik.
7
+ - Pelanggan (subscriber) akan menerima nilai semasa secara automatik apabila mula melanggan.
8
+
9
+ Fungsi ini biasanya digunakan dalam [senario](../concept/scenario.md) dengan corak berikut:
10
+
11
+ - Digunakan untuk mengekalkan sebarang nilai dalam domain secara kekal.
12
+ - Anda boleh menggunakan nilai keadaan dalam senario dengan menulis atau membaca daftar keadaan (state-write, state-read).
13
+ - Apabila menerbitkan nilai kepada klien, jika terdapat daftar keadaan dengan nama yang sama seperti tag penerbitan, nilainya akan dikemas kini secara automatik.
14
+
15
+ ---
16
+
3
17
  [Daftar keadaan(state-register)](../concept/state-register.md) adalah skrin yang mentakrif nilai-nilai keadaan dengan makna tertentu.
4
18
 
5
19
  - Fungsi ini biasanya digunakan oleh tugas [senario](../concept/scenario.md) seperti [state-write](../task/state-write.md), [state-read](../task/state-read.md).
@@ -14,11 +28,8 @@
14
28
  - Boleh memasukkan teks bebas, bertujuan untuk pengguna membezakan antara keadaan-keadaan
15
29
  - TTL (Time To Live)
16
30
  - Boleh menentukan masa sah nilai keadaan dalam unit detik.
17
- - Jika nilai TTL lebih dari 0, maka dianggap telah
18
-
19
- menetapkan TTL.
20
-
21
- - Nilai keadaan yang terakhir ditetapkan akan tidak sah setelah masa TTL berlalu
31
+ - Jika nilai TTL lebih dari 0, maka dianggap telah menetapkan TTL.
32
+ - Nilai keadaan yang terakhir ditetapkan akan tidak sah setelah masa TTL berlalu
22
33
  - Nilai keadaan (state)
23
34
  - Maksudnya nilai semasa keadaan itu.
24
35
  - Tarikh pengubahsuaian (wrote at)
@@ -1,5 +1,19 @@
1
1
  # 状态登记册 (StateRegister)
2
2
 
3
+ 状态登记册(state-register)用于**在域内永久(持久)地维护某个状态值**。
4
+
5
+ - 状态值会被永久保存。
6
+ - 如果设置为自动发布,则值发生变化时会自动触发发布(事件推送)。
7
+ - 订阅者在开始订阅时会自动收到当前值。
8
+
9
+ 该功能主要在[场景](../concept/scenario.md)中以如下模式使用:
10
+
11
+ - 用于在域内持久化任何值。
12
+ - 通过写入或读取状态登记册(state-write, state-read),可以在场景中利用状态值。
13
+ - 当向客户端发布某个值时,如果存在与发布 tag 同名的 state-register,则会自动更新其值。
14
+
15
+ ---
16
+
3
17
  [状态登记册(state-register)](../concept/state-register.md)是一个定义具有特定意义状态值的界面。
4
18
 
5
19
  - 这个功能通常由[场景](../concept/scenario.md)中的[state-write](../task/state-write.md)、[state-read](../task/state-read.md)任务使用。
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@things-factory/integration-ui",
3
- "version": "9.0.1",
3
+ "version": "9.0.4",
4
4
  "main": "dist-server/index.js",
5
5
  "browser": "dist-client/index.js",
6
6
  "things-factory": true,
@@ -41,9 +41,9 @@
41
41
  "@operato/utils": "^9.0.0",
42
42
  "@things-factory/export-base": "^9.0.0",
43
43
  "@things-factory/import-base": "^9.0.0",
44
- "@things-factory/integration-base": "^9.0.1",
45
- "@things-factory/personalization": "^9.0.0",
44
+ "@things-factory/integration-base": "^9.0.4",
45
+ "@things-factory/personalization": "^9.0.2",
46
46
  "d3": "^7.8.5"
47
47
  },
48
- "gitHead": "784f6d6072cbbcfc5fcbe18f48e85521e933ecdd"
48
+ "gitHead": "19ea4dea609aab5f5827af1c5586a1b843f3252a"
49
49
  }
@@ -12,6 +12,7 @@
12
12
  "button.unschedule-task": "unschedule task",
13
13
  "field.active": "active",
14
14
  "field.api_url": "API URL",
15
+ "field.auto-publish": "auto publish",
15
16
  "field.connection": "connection",
16
17
  "field.crontab": "crontab",
17
18
  "field.edge-server": "edge server",
@@ -8,10 +8,11 @@
8
8
  "button.start monitor": "モニタリング開始",
9
9
  "button.stop": "停止",
10
10
  "button.stop monitor": "モニタリング終了",
11
- "button.schedule-task": "jadualkan tugas",
12
- "button.unschedule-task": "batalkan jadual tugas",
11
+ "button.schedule-task": "タスクをスケジュール",
12
+ "button.unschedule-task": "タスクのスケジュールを解除",
13
13
  "field.active": "アクティブ化",
14
14
  "field.api_url": "API URL",
15
+ "field.auto-publish": "自動公開",
15
16
  "field.break_main": "BreakMain",
16
17
  "field.connection": "連結",
17
18
  "field.crontab": "クロン タブ",
@@ -82,7 +83,7 @@
82
83
  "label.reject-unauthorized": "証明書使用",
83
84
  "label.scenario": "シナリオ",
84
85
  "label.script": "スクリプト",
85
- "label.search-params": "search params",
86
+ "label.search-params": "検索パラメータ",
86
87
  "label.second": "秒",
87
88
  "label.second by second": "秒単位",
88
89
  "label.selectors": "selectors",
@@ -12,6 +12,7 @@
12
12
  "button.unschedule-task": "스케쥴 취소",
13
13
  "field.active": "활성화",
14
14
  "field.api_url": "API URL",
15
+ "field.auto-publish": "자동 퍼블리시",
15
16
  "field.break_main": "BreakMain",
16
17
  "field.connection": "연결",
17
18
  "field.crontab": "크론탭",
@@ -13,6 +13,7 @@
13
13
  "button.unschedule-task": "batalkan jadual tugas",
14
14
  "field.active": "aktif",
15
15
  "field.api_url": "URL API",
16
+ "field.auto-publish": "terbitan automatik",
16
17
  "field.connection": "sambungan",
17
18
  "field.crontab": "crontab",
18
19
  "field.edge-server": "pelayan tepi",
@@ -12,6 +12,7 @@
12
12
  "button.unschedule-task": "取消安排任务",
13
13
  "field.active": "激活",
14
14
  "field.api_url": "API URL",
15
+ "field.auto-publish": "自动发布",
15
16
  "field.connection": "连接",
16
17
  "field.crontab": "crontab",
17
18
  "field.edge-server": "边缘服务器",