Skip to content

@W-18999015 footer component updated for shopper consents email marketing subscription hooks#3471

Merged
mitesh-patel-crm merged 4 commits intofeature/develop-shopper-consent-marketing-preferencesfrom
mitesh-patel-crm/w-18999015-shopper-consents-footer-only
Nov 18, 2025
Merged

@W-18999015 footer component updated for shopper consents email marketing subscription hooks#3471
mitesh-patel-crm merged 4 commits intofeature/develop-shopper-consent-marketing-preferencesfrom
mitesh-patel-crm/w-18999015-shopper-consents-footer-only

Conversation

@mitesh-patel-crm
Copy link
Collaborator

W-18999015 Footer Component hooks for Marketing Consent.
Queries shopper-consents SCAPI for tags=email_capture, and then updates all subscriptions to opt_in given the input email address as the contactPointValue.

Description

Types of Changes

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Documentation update
  • Breaking change (could cause existing functionality to not work as expected)
  • Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

  • Removing a public function or component or prop
  • Adding a required argument to a function
  • Changing the data type of a function parameter or return value
  • Adding a new peer dependency to package.json

Changes

  • (change1)

How to Test-Drive This PR

  • (step1)

Checklists

General

  • Changes are covered by test cases
  • CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

  • There are no changes to UI

or...

Localization

  • Changes include a UI text update in the Retail React App (which requires translation)

Queries shopper-consents SCAPI for tags=email_capture, and then updates all subscriptions to opt_in given the input email address as the contactPointValue.
@mitesh-patel-crm mitesh-patel-crm requested a review from a team as a code owner November 14, 2025 11:12
@cc-prodsec
Copy link
Collaborator

cc-prodsec commented Nov 14, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@mitesh-patel-crm mitesh-patel-crm requested review from knhage and kzheng-sfdc and removed request for a team November 14, 2025 11:12
const tagList = tags.join(', ')
console.error(
`[useEmailSubscription] No subscriptions found for tag(s) "${tagList}" and channel "email". ` +
`Please configure subscriptions in Business Manager with one of these tags: ${tagList}.`
Copy link
Contributor

Choose a reason for hiding this comment

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

This error seems to be more suitable for server side logging than for browser/shopper.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yeah, it shouldn't say anything about Business Manager!! Let me fix that.

*
* Subscriptions are fetched on-demand when the user clicks submit, not on component mount.
*
* This allows marketers to configure subscriptions in Business Manager without code changes.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@kzheng-sfdc is it ok to reference Business Manager here? I see "Business Manager" referenced in a README file for pwa-kit. I could also be more vague here instead.

@mitesh-patel-crm mitesh-patel-crm merged commit 1ec047a into feature/develop-shopper-consent-marketing-preferences Nov 18, 2025
13 of 16 checks passed
@mitesh-patel-crm mitesh-patel-crm deleted the mitesh-patel-crm/w-18999015-shopper-consents-footer-only branch November 18, 2025 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants