VACMS 19842 - conditional rendering of data-widget-type div or full-width-banners based on CMS toggle

[eselkin]

Summary

• Puts div for React widget injection next to full width banners in header.html and makes it conditional based on CMS toggle
• Sitewide team
• CMS toggle FEATURE_BANNER_USE_ALTERNATIVE_BANNERS

Related issue(s)

• VAMC real-time banners: cut over vets-website FE to using vets-api endpoint && make content-build use the new CMS feature toggle va.gov-cms#19842

Testing done

• Conditionally renders the div with the widget type for using vets-website banner when toggled feature is on and uses standard existing div with va-banner from graphql if off.
• Manually tested two builds on a tugboat

Screenshots

Build with FEATURE_BANNER_USE_ALTERNATIVE_BANNERS: true but tugboat doesn't build the new v-w so div is blank (but still no full-width-banner from liquid template)

Build with FEATURE_BANNER_USE_ALTERNATIVE_BANNERS: false

What areas of the site does it impact?

Affects the pages in VAMC systems (including va-manila-clinic which is a system to itself) for the full-width banners under the header

Acceptance criteria

• When CMS feature toggle FEATURE_BANNER_USE_ALTERNATIVE_BANNERS is enabled, in content-build, the existing prod build of VAMC BwSU should disappear across ALL templates

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

Check a tugboat build with /admin/config/system/feature_toggle on and off for FEATURE_BANNER_USE_ALTERNATIVE_BANNERS
this was done on https://main-pjrkdo5kzgprzxpfz31rnvzleiegcmh4.demo.cms.va.gov/admin/config/system/feature_toggle

[SnowboardTechie]

LGTM

[rmessina1010]

LGTM