-
Notifications
You must be signed in to change notification settings - Fork 195
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
refactor!: manifest v3 support #1051 #1124
Conversation
82bc8a9
to
9a2c69f
Compare
fc57c7d
to
363a87c
Compare
363a87c
to
2804f1f
Compare
2804f1f
to
e958323
Compare
e958323
to
686eb1a
Compare
686eb1a
to
63f570a
Compare
63f570a
to
5c1c617
Compare
5c1c617
to
4ce4034
Compare
🚀 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 ⚡️builds@getalby.com (don't forget to provide your name) Don't forget: keep earning sats! |
4ce4034
to
cc8fcc7
Compare
cc8fcc7
to
a6bdc08
Compare
a6bdc08
to
902713c
Compare
7be75ce
to
18fa751
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Yup, let me have a look Findings: RESULT: fixed ✅ |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@@ -3,11 +3,11 @@ import type { MessageReset } from "~/types"; | |||
import state from "../../state"; | |||
|
|||
const reset = async (message: MessageReset) => { | |||
await state.getState().password(null); |
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.
@im-adithya please check if this is correct. Just adjusted it according to the mv3 way of handling the password.
COMMANDO / LNMESSAGE UPDATEStatusCommando was already tested and checked ✅ above. FindingsWhat happened in between?: lnmessage v.01.0 Assumption is we do not have a SolutionReverting back to lnmessage v0.0.19 is fixing this for now |
CURRENT FINDINGSALL GOOD SO FARAxios doesn't seem to work in background-scripts, might need to switch (back) to fetch:https://stackoverflow.com/questions/66305856/typeerror-adapter-is-not-a-function-error-when-using-axios-and-webpack-in-chrom/70206333#70206333
No (extrenal) imagesNo external API callsJust switching current code to use web workers doesn't workDescribe the changes you have made in this PR
Trying to prepare the switch to v3
Link this PR to an issue
Fixes #1051
Type of change (Remove other not matching type)
refactor
: Breaking refactorHow has this been tested?
...not yet
Checklist