-
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 the ZeroDataNotification
to use the new lighter Notification
component.
#9184
Comments
AC ✔️ |
IB ✔️ |
QA Update ❌Tested on dev environment. Issue 1: ( Zero data notification is not showing if only SC is in gathering data state and Analytics is in zero date state). Issue 2> If the zero data notification is not dismissed and the user opens the dashboard in a new tab or window, the zero data state notification does not appear on the first load. The user must refresh the page for the notification to appear. This behavior is observed on both the main and entity dashboards. However, this issue does not occur with the gathering data state notification. Recording.1320.mp4Issue 3: View only dashboard >If only one module (either SC or Analytics) is shared initially and that module is in either the gathering or zero data state, and if the user dismisses the notice for the gathering or zero data state for that module, then when the second module is shared and it is also in the same data state as the first module, a notification will not appear for the second module because the notice has already been dismissed. |
Issue 1 and Issue 3 are current behaviour already (on the last release). So this behaviour is fine. Issue 2: I am not able to reproduce this. I tried this when SC is in Zero Data and when Analytics alone is in Zero data, and in both cases, the notification appeared immediately after module set up without requiring a page load or refresh. Could you please create a screencast (with the URL bar present as well always). Even if this was the case, I feel this also won't be a release blocker as it is minor and can be fixed in the next release. Thank you! c.c. @aaemnnosttv |
QA Update ✅
|
Feature Description
This issue focuses on refactoring the
ZeroDataNotification
using the newNotification
wrapper component along with the newly introduced layout component in #9071.Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
ZeroDataNotification
to use the newNotification
wrapper component introduced in Refactor theGatheringDataNotification
to use a newly refactored version of theBannerNotification
component. #9071.GatheringDataNotification
to use a newly refactored version of theBannerNotification
component. #9071.ZeroDataNotification
should remain the same, i.e. all existing GA events should be fired and the design/links should work as before.Implementation Brief
assets/js/components/notifications/ZeroDataNotification.js
assets/js/components/notifications/GatheringDataNotification.js
for the exampleBannerNotification
componentid
andNotification
Notification
component passed as the propNotificationWithSmallSVG
can be reused. Refactor this notification to allow the usage of only theDismiss
component.assets/js/googlesitekit/notifications/components/common/
to assemble the notification using the existing props used to forBannerNotification
.LearnMoreLink
component can append the Learn more link required in the description.Test Coverage
QA Brief
Remind me later
button and test the dismissal. Ensure the notification is correctly dismissed - a new item will appear in thewp_googlesitekitpersistent_dismissed_items
record inwp_usermeta
in the database.SetupSuccessBannerNotification
or theGatheringDataNotification
is active - they should take precedence over the Zero Data notification.GatheringDataNotification
to use a newly refactored version of theBannerNotification
component. #9071 as the code for this issue touches the code from that issue as well.Changelog entry
The text was updated successfully, but these errors were encountered: