5 commits

Author	SHA1	Message	Date
Rusty Russell	2914d3adfc	plugins: allow plugins to get per-connection deprecated state. ... Unfortunately, this is awkward: we just copy through most requests, so we can't easily add a "deprecation" field to each one. So we do a notification if the next command has a different deprecation status than the global one, but that requires opt-in from the plugin. We didn't previously document the subscriptions array, so do that now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Plugins: `deprecated_oneshot` notifiction subscription to change deprecated status for a single command.	2024-01-26 10:30:22 +10:30
Erik De Smedt	36f69a1a98	Docs: Add custommsg notification	2023-12-16 11:36:42 +10:30
Erik De Smedt	acce3b1b32	Fix docs for invoice_payment hook and notification ... The data-format changed in 2019. The field `amount_msat` was renamed to `msat` (See 2907e430d5) The data-format changed again in november 2023. The content of the field `amount_msat` was changed. It was a string `"1000msat"` and became a number `1000`. (See 0b23133ab2) The current documentation still mentions the data-format before 2907e430d5. I've updated the docs to reflect the latest changes. I've also incluced a short mention of 0b23133ab2 to help help developers create plugins that work both pre 23.11 and post 23.11.	2023-12-12 16:53:59 +01:00
Chris Guida	8bbf2342f7	lightningd: adapt invoice_try_pay declaration for onchain payment. ... i.e. `set` may be NULL, so we need to explicitly hand the amount. We also add an outpoint.	2023-10-26 19:11:17 +10:30
Adi Shankara	b2caa56c27	update new documentation and move to doc/	2023-07-16 12:59:40 +09:30

Renamed from doc/guides/Developer-s Guide/plugin-development/event-notifications.md (Browse further)