-
Notifications
You must be signed in to change notification settings - Fork 401
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
Mezo test build #3800
Draft
hyphenized
wants to merge
58
commits into
main
Choose a base branch
from
test-claimer-build
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Mezo test build #3800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will control visibility and behaviour of banners and other UI elements
This sets a recurrent alarm to hit the API and check claim state unless the wallet is not eligible or the campaign has already been finished. If eligible, users receive a notification based on their claim completion.
Transactions must have been completed and target the borrower contract on the mezo network.
This is used by posthog to distinguish users
- onDismiss is no longer passed as an options to the extension API - Fixed a race condition in NotificationService state initialization - Fixed the notifications settings toggler As MV3 requires permissions to be requested during a user action, the prompt for user permission no longer works if triggered through a redux thunk that executed in the background.
Sets a visibility assertion to confirm element exists before synchronously asserting value
Exclusively used for newly added builtin networks
Moves test network visibility user setting to preference service and sets force toggles it to display on all new and existing installs
This PR moves the testnet visibility setting to the preference service, and sets a migration to enable it on all existing and new installs. ## Testing - [ ] On a new install, check testnets shows up by default on network switcher - [ ] On existing install, after update testnets should show up Latest build: [extension-builds-3793](https://github.com/tahowallet/extension/suites/35160394180/artifacts/2686423977) (as of Tue, 04 Mar 2025 05:05:23 GMT).
This makes it easier to manually clear notifications
This moves campaign related logic out of the main service into a dedicated service. It also causes dismissing campaign banners to clear and stop triggering notifications about the same topic. Campaign state is kept within the service db and updates are pushed to state in redux. Latest build: [extension-builds-3794](https://github.com/tahowallet/extension/suites/35331061341/artifacts/2708368343) (as of Fri, 07 Mar 2025 03:08:56 GMT).
Async checks should help with request deduplication, this also queues a campaign status check if a user connects to the dapp and the service still hasn't retrieved campaign status so the sats drop endpoint is properly called.
Removes a collection from state if NFT count is defined and is zero
f3f5f5f
to
af37587
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing env
Latest build: extension-builds-3800 (as of Fri, 14 Mar 2025 23:54:04 GMT).