-
Notifications
You must be signed in to change notification settings - Fork 34
1812 migrate alert component to wdn6.0 version 2 #1814
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
base: 6.0
Are you sure you want to change the base?
Conversation
… plain JavaScript. Fixes #1812.
… on CMS), I’ve removed the logic that sets the unlAlertsData cookie, as it interferes with how WDN5 handles it. I’ll work on new logic for storing alert data in the cookie, which will be deployed once all sites have migrated to WDN6.
… JavaScript needs to be loaded. Two new cookie names were created to prevent conflicts with existing WDN5 alert cookies, as some sites will remain on WDN5 for a while until they migrate. Fixes 1812.
…igrate-alert-component-to-wdn6.0-version-2
|
| ); | ||
| } | ||
|
|
||
| async #checkIfFetchCallNeeded() { |
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.
If I have two tabs open and if there is no data in unlcap.js then both tabs will be fetching the data. If there is data in unlcap.js then it preforms as intended. This is leading to unneeded requests for unlcap.js. If there is no data in unlcap.js then the cookie needs to still be set so that these unneeded requests are not being sent
tommyneu
left a comment
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.
Making sure to write this down, the ID unlalert is being used in multiple elements



Migrated alert component to wdn framework 6. Replaced all jQuery with plain JavaScript. Fixed alert close icon showing after refresh.
Version 2 contains: Saving alert data to a cookie to reduce the number of times the alert JavaScript needs to be loaded. Two new cookie names were created to prevent conflicts with existing WDN5 alert cookies, as some sites will remain on WDN5 for a while before migrating.
Closes #1812
Closes #1757