You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the context of discussing the feature of paginated transactions data (incoming/outgoing) for the lightning-browser-extension with @reneaaron recently, I was doing some research about the API capabilities of the different connectors we use. For a lot of connectors we don't even support displaying invoices yet. LND and CLN have limited support so far, but might have support soon. I also checked the lndhub.go codebase and found there is no support for paginated invoices yet. The response is limited to the latest 100 entries.
However as we have full control of the code, it is not difficult to implement and we might want to use paginated transactions at least for Alby accounts, I propose to implement it.
As I debugged the codebase recently and got curious I implemented a draft version. Please have a look. If you think it generally makes sense, I am happy to receive some feedback and move along implementing it.
Important to consider is, this would lead to breaking changes as it changes the API response object for the invoices endpoint.
In the context of discussing the feature of paginated transactions data (incoming/outgoing) for the lightning-browser-extension with @reneaaron recently, I was doing some research about the API capabilities of the different connectors we use. For a lot of connectors we don't even support displaying invoices yet. LND and CLN have limited support so far, but might have support soon. I also checked the lndhub.go codebase and found there is no support for paginated invoices yet. The response is limited to the latest 100 entries.
However as we have full control of the code, it is not difficult to implement and we might want to use paginated transactions at least for Alby accounts, I propose to implement it.
As I debugged the codebase recently and got curious I implemented a draft version. Please have a look. If you think it generally makes sense, I am happy to receive some feedback and move along implementing it.
Important to consider is, this would lead to breaking changes as it changes the API response object for the invoices endpoint.
lujakob#2
The text was updated successfully, but these errors were encountered: