-
Notifications
You must be signed in to change notification settings - Fork 284
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 UnsatisfiedScopesAlertGTE
to use the new Notifications datastore and "layout" components
#8979
Labels
Comments
jimmymadon
added
Type: Enhancement
Improvement of an existing feature
Team S
Issues for Squad 1
labels
Jul 8, 2024
tofumatt
changed the title
Refactor the UnsatisfiedScopesAlertGTE to use the new Notifications datastore
Refactor Jul 23, 2024
UnsatisfiedScopesAlertGTE
to use the new Notifications datastore
jimmymadon
changed the title
Refactor
Refactor Aug 12, 2024
UnsatisfiedScopesAlertGTE
to use the new Notifications datastoreUnsatisfiedScopesAlertGTE
to use the new Notifications datastore and "layout" components
AC ✔️ |
IB ✔️ |
This was referenced Sep 2, 2024
QA Update ❌Tested on dev environment. Issue - Alignment of |
18 tasks
QA Update ✅
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature Description
This issue refactors another (the second) "Error" notification in Site Kit as part of Phase 1 of the Banner Notifications Refactoring epic. It should refactor the
UnsatisfiedScopesAlert
so that it uses the new datastore infrastructure to register and queue the notification. It should also use newer lighter "layout" and "common" components that replace the bloatedBannerNotification
component as per the pattern introduced in #9071.Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
UnsatisfiedScopesAlertGTE
component should be refactored so that it is registered and rendered (queued) using the newcore/notifications
datastore.ErrorNotifications
) but only via the genericgetQueuedNotifications
selector.BannerNotification
component. Instead, it should be rendered using the newNotification
component wrapper and a simpler "layout" component that solely encapsulates its structure and design.Implementation Brief
assets/js/components/notifications/UnsatisfiedScopesAlertGTE.js
assets/js/components/notifications/UnsatisfiedScopesAlert.js
for the example/starting pointBannerNotification
componentid
andNotification
Notification
component passed as the propassets/js/googlesitekit/notifications/components/common/
andlayout
to assemble the notification using the existing props used to forBannerNotification
assets/js/googlesitekit/notifications/register-defaults.js
UnsatisfiedScopesAlert
checkRequirements
transfer the existing checks fromassets/js/components/notifications/ErrorNotifications.js
UnsatisfiedScopesAlert
notificationUnsatisfiedScopesAlertGTE
from theassets/js/components/notifications/ErrorNotifications.js
Test Coverage
UnsatisfiedScopesAlert
as an exampleQA Brief
https://www.googleapis.com/auth/tagmanager.readonly
from the list ofwp_googlesitekit_authscopes
and to Connect GA4. Try using the following snippet within your database for this record.wp_googlesitekit_additional_auth_scopes
record for the user is also deleted or removed if it exists.Changelog entry
The text was updated successfully, but these errors were encountered: