Connection nodes speak of listener and sender, and of send_queue_size
mqtt and http take websocket's vocabulary: their Mode is LISTENER/SENDER, default names read mqtt_listener_… and http_listener_…, and mqtt's publish_queue_size is send_queue_size. No alias stays behind, so the flow store rewrites the old setting in every published and draft mqtt node when it opens, in the same migration as trigger → debounce. Every mqtt and http setting carries a one-line description for the editor, and the node-types reference uses one wording for direction and says that an http sender publishes a JSON object response on its outputs.
This commit is contained in:
@@ -121,7 +121,13 @@ class WebSocketNode(Node):
|
||||
),
|
||||
)
|
||||
# Same as the mqtt node: a device that wraps its reading in an object.
|
||||
json_key: str | dict[str, str] = ""
|
||||
json_key: str | dict[str, str] = Field(
|
||||
default="",
|
||||
description=(
|
||||
"Key to lift out of a JSON object frame, for every port or as "
|
||||
'{"port": "key"}.'
|
||||
),
|
||||
)
|
||||
|
||||
@classmethod
|
||||
def target_key(cls, params: dict[str, Any]) -> str | None:
|
||||
|
||||
Reference in New Issue
Block a user