Skip to content
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

MWPW-157147: Dynamic Nav Status Button #2920

Open
wants to merge 1 commit into
base: stage
Choose a base branch
from

Conversation

JasonHowellSlavin
Copy link
Contributor

  • Adds a status button to appear in the nav to inform content QA and QA whether or not the Dynamic Nav is active and to provide additional information about Dynamic Nav and it's settings.
  • The experience is set for tablet and up, since the core user is QA.

Context:
The milo repo does not have the dynamicNavKey in the config, so the first two links will not show the feature.

Resolves: MWPW-157147

Test URLs:

Bacom

@JasonHowellSlavin JasonHowellSlavin added run-nala Run Nala Test Automation against PR needs-verification PR requires E2E testing by a reviewer labels Sep 19, 2024
Copy link

codecov bot commented Sep 19, 2024

Codecov Report

Attention: Patch coverage is 97.85714% with 3 lines in your changes missing coverage. Please review.

Project coverage is 96.24%. Comparing base (c3c9bcc) to head (2b4175d).

Files with missing lines Patch % Lines
libs/utils/utils.js 25.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##            stage    #2920      +/-   ##
==========================================
- Coverage   96.24%   96.24%   -0.01%     
==========================================
  Files         236      237       +1     
  Lines       54254    54391     +137     
==========================================
+ Hits        52217    52346     +129     
- Misses       2037     2045       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -1126,6 +1126,10 @@ export async function loadDeferred(area, blocks, config) {
import('../features/personalization/preview.js')
.then(({ default: decoratePreviewMode }) => decoratePreviewMode());
}
if (config?.dynamicNavKey) {
const { default: loadDNStatus } = await import('../features/dynamic-navigation/status.js');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this file will load on prod even though you're not showing the status there. Would be good to have an env check here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was following mep's pattern and have the env check in the main function, but can move it here.

transition-duration: 0.2s;
}

.dns-badge.dns-open::after{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.dns-badge.dns-open::after{
.dns-badge.dns-open::after {

rotate: 180deg;
}

.dynamic-nav-status p{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.dynamic-nav-status p{
.dynamic-nav-status p {

width: 100%;
}

.dynamic-nav-status .disable-values caption{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.dynamic-nav-status .disable-values caption{
.dynamic-nav-status .disable-values caption {

border-bottom: 1px solid white;
}

.dynamic-nav-status .disable-values{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.dynamic-nav-status .disable-values{
.dynamic-nav-status .disable-values {

Copy link
Contributor

This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-verification PR requires E2E testing by a reviewer run-nala Run Nala Test Automation against PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants