You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: adapters/json-rpc-spec.md
+127Lines changed: 127 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,6 +277,133 @@ An empty `registers` array is valid and starts polling with no registers configu
277
277
278
278
---
279
279
280
+
### `adapter.registerSchema`
281
+
282
+
Returns the schema for register expressions — what fields make up a register address, how they should be rendered in the UI, and available data types. Call this after `adapter.describe` to discover how to build the register input UI.
|`addressSchema`| JSON Schema describing the address input fields. The core renders this with `SchemaFormWidget`|
321
+
|`dataTypes`| Array of available data types. Each entry has `id` (used in expression strings) and `label` (UI display) |
322
+
|`defaultDataType`| The `id` of the type to pre-select in the UI |
323
+
324
+
The `addressSchema` follows standard JSON Schema conventions. The core application uses it to dynamically generate the address input portion of the register dialog, so it must accurately describe all required fields and their constraints.
325
+
326
+
---
327
+
328
+
### `adapter.describeRegister`
329
+
330
+
Parses a register expression into structured fields and returns a human-readable description. Used by the core to display register details in tables and tooltips without understanding protocol-specific address formats.
0 commit comments