Future CLN API deprecations can negatively affect PeerSwap

[grubles]

This describes a broader issue with how PeerSwap handles changes to the CLN API. CLN defaults to keeping the deprecated fields turned on for a period of time before they are fully removed in order to minimize disruptions / breakage. However, some users may turn off these fields by setting allow-deprecated-apis=false in their CLN configs. This may cause PeerSwap to break

Currently the plan is to try and detect if deprecated API fields are turned off by reading the CLN config (#230) and exiting the plugin completely to be safe, but this is only a temporary solution until we can handle API changes better.

[grubles]

Would adding a separate CLN instance with allow-deprecated-apis=false to the CI help to check for breakage?

[YusukeShimizu]

I think the solution is to set allow-deprecated-apis=false in the integration test and fix the cases where it doesn't work properly.

Additionally, looking towards the future, the ideal scenario would be for the API interface to be automatically generated and capable of detecting updates.