Christian Decker 8898511cf6 cln-plugin: Defer binding the plugin state until after configuring ... We had a bit of a chicken-and-egg problem, where we instantiated the `state` to be managed by the `Plugin` during the very first step when creating the `Builder`, but then the state might depend on the configuration we only get later. This would force developers to add placeholders in the form of `Option` into the state, when really they'd never be none after configuring. This defers the binding until after we get the configuration and cleans up the semantics: - `Builder`: declare options, hooks, etc - `ConfiguredPlugin`: we have exchanged the handshake with `lightningd`, now we can construct the `state` accordingly - `Plugin`: Running instance of the plugin Changelog-Changed: cln-plugin: Moved the state binding to the plugin until after the configuration step		2022-09-25 15:13:12 +02:00
..
cln-plugin-startup.rs	cln-plugin: Defer binding the plugin state until after configuring	2022-09-25 15:13:12 +02:00