-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
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
chore: unify connector functions #1713
Conversation
We throw an error on the error case
🚀 Thanks for the pull request! Here are the current build files for testing: Download and unzip the file for your browser. Refer to the readme for detailed install instructions. This build is brought to you by:
Want to sponsor the next build? send some sats to ⚡️[email protected] (don't forget to provide your name) Don't forget: keep earning sats! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This makes a lot of sence
Uhm, at one point in time the returned Error was used to trigger and show an error-toast. But this doesn't seem to work anymore (on master) so this change makes the current state better. |
I don't fully get your last comment. what's the suggestion? |
No suggestion. Your PR improves the current situation. This is good. Question: |
why does the user not get feedback? https://github.com/getAlby/lightning-browser-extension/pull/1713/files#diff-d07eb0245fd06ccaf878d056614cc4a944a918bbdd4267619cf3eb264bdd7eb3 -> here for example: both return error: message in the error case. |
hmm. your error is strange. because getInvoices should be implemented on Lndhub |
All good, that was just a test by replacing the function |
When #1080 was merged it looked like this: |
naja, can you explain that? that PR is from Jul 26. so I don't know what you try to say.
we still don't support it in all. and if we broke something we should not say: 🤷 we do most ... |
:D So, this is related to this PR because by looking at this I noticed that apparently "showing the toast to the user" does not work anymore. We need to decide we want to show something to the user if their connector doesn't support this yet.
It's a decision of priorization |
this seems broken in master, no idea when/how it got broken (that could use investigation, because I have no idea how it could have worked before) this PR actually fixes this I think for the invoices. at least it should. https://github.com/getAlby/lightning-browser-extension/pull/1713/files#diff-167ef8f8c43cebe91d5e71f3724e953a69277ab2c9b30af8dfc47a0707613544 what do we need to prioritize? |
We throw an error on the error case
Link this PR to an issue [optional]
fixes #1712
Type of change
(Remove other not matching type)
fix
: Bug fix (non-breaking change which fixes an issue)How has this been tested?
needs testing