We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NWC and webln are not fully compatible. currently our NWC client is webln compatible which limits us using some NWC details
We should split this up and make a NWC client independent of WebLN.
Maybe we make a NWC class and the NWC webln provider inherits from that one?
The text was updated successfully, but these errors were encountered:
Or @bumi 's other suggestion:
maybe have a NWC client and a NWC WebLN Provider uses that and returns the webln required data.
Sorry, something went wrong.
rolznz
Successfully merging a pull request may close this issue.
NWC and webln are not fully compatible.
currently our NWC client is webln compatible which limits us using some NWC details
We should split this up
and make a NWC client independent of WebLN.
Maybe we make a NWC class and the NWC webln provider inherits from that one?
The text was updated successfully, but these errors were encountered: