mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-03-03 18:57:06 +01:00
doc: document custommsg hook now chainable
This commit is contained in:
parent
8e71c7a1f1
commit
4e8d3f395b
1 changed files with 2 additions and 5 deletions
|
@ -1218,11 +1218,8 @@ ignored by nodes (see ["it's ok to be odd" in the specification][oddok] for
|
||||||
details). The plugin must implement the parsing of the message, including the
|
details). The plugin must implement the parsing of the message, including the
|
||||||
type prefix, since c-lightning does not know how to parse the message.
|
type prefix, since c-lightning does not know how to parse the message.
|
||||||
|
|
||||||
The result for this hook is currently being discarded. For future uses of the
|
Because this is a chained hook, the daemon expects the result to be
|
||||||
result we suggest just returning `{'result': 'continue'}`.
|
`{'result': 'continue'}`. It will fail if something else is returned.
|
||||||
This will ensure backward
|
|
||||||
compatibility should the semantics be changed in future.
|
|
||||||
|
|
||||||
|
|
||||||
### `onion_message` and `onion_message_blinded`
|
### `onion_message` and `onion_message_blinded`
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue