-
Notifications
You must be signed in to change notification settings - Fork 337
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
fix: allow subscribing to owned but not added safes #3429
Conversation
Branch previewβ Deploy successful! |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
π¦ Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. π€ π Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! Fifteen Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. |
Coverage report
Show new covered files π£
Show files with reduced coverage π»
Test suite run success1401 tests passing in 194 suites. Report generated by π§ͺjest coverage report action from cdbaf19 |
β¦ notification settings
restore removed test
ESLint Summary View Full Report
Report generated by eslint-plus-action |
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.
Considering that we have the notification feature for a while now, how complex the PushNotificationBanner
component is and that we already received feedback in the past to reduce the number of popups I would be in favour of removing it completely. Lets discuss it with the team.
src/components/settings/PushNotifications/GlobalPushNotifications.tsx
Outdated
Show resolved
Hide resolved
src/components/settings/PushNotifications/PushNotificationsBanner/index.tsx
Outdated
Show resolved
Hide resolved
@jmealy discussed it this morning and others are also in favour of removing the banner. @katspaugh suggests to rename the "Settings" button to "Push notification settings" |
brilliant, thanks Usame π |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
@mike10ca do we need to update something in Testrail now that the Push Notification Banner has been removed? |
@usame-algan no, since automation does not cover notifications to date. |
The rest looks good Safe you added but don't own doesn't show up in the global settings If the button will remain as "Settings" then the ticket can be merged. If not, change the test and don't put it in QA, just merge it |
What it solves
Resolves #3288
How this PR fixes it
How to test it
Checklist