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

feat(MI-86): updating uploads/creatives API with personalized QR codes in campaigns #485

Merged
merged 6 commits into from
Mar 6, 2024

Conversation

amaan-lob
Copy link
Contributor

@amaan-lob amaan-lob commented Mar 1, 2024

Fixes MI-86
Functionality already exists, just updating copy to clarify how to use personalized QR codes per recipient in a campaign.

Checklist

  • Up to date with main
  • All the tests are passing
    • Delete all resources created in tests
  • Prettier
  • Spectral Lint
  • npm run bundle outputs nothing suspect
  • npm run postman outputs nothing suspect

Changes

  • clarify how to specify unique redirect URLs per recipient when using QR codes in campaigns
  • update request samples to include qr_code_redirect_url

Areas of Concern (optional)

@amaan-lob amaan-lob requested a review from a team as a code owner March 1, 2024 18:31
@amaan-lob amaan-lob changed the title feat(MI-86): feat(MI-86): updating uploads/creatives API with personalized QR codes in campaigns Mar 1, 2024
description: |
Redirect all mail recipients to either a single URL or specify a unique URL for each recipient.
To redirect all mail recipients in a campaign to the same URL, assign the desired URL to this field.
To redirect each mail recipient to a unique URL, leave this field empty and specify the redirect link for each row in the audience file. Then, when creating a new upload, map this column to the `qr_code_redirect_url` key in the `mergeVariableColumnMapping` property.
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably want to retain the help center link on audience file.

Copy link
Contributor

@juanfriss juanfriss left a comment

Choose a reason for hiding this comment

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

you will need to upgrade package.json too

@amaan-lob
Copy link
Contributor Author

you will need to upgrade package.json too

Hey @juanfriss, do we need to include output files from the npm run bundle and npm run postman commands since I see they are executed in the Deploy GHA?

@juanfriss
Copy link
Contributor

I think you don't as "The bundled version is generated as part of CI/CD"

@kevinpjones
Copy link
Contributor

I think you'll need npm run bump-version, as it updates version in package.json as well as the spec yaml

Copy link

guardrails bot commented Mar 6, 2024

⚠️ We detected 7 security issues in this pull request:

Vulnerable Libraries (7)
Severity Details
High pkg:npm/[email protected] (t) upgrade to: > 3.2.1
High pkg:npm/[email protected] (t) upgrade to: > 4.15.1
High pkg:npm/@redocly/[email protected] (t) upgrade to: > 1.10.3
High pkg:npm/[email protected] (t) upgrade to: > 0.13.21
High pkg:npm/[email protected] (t) upgrade to: > 6.5.1
High pkg:npm/[email protected] (t) upgrade to: > 4.2.2
High pkg:npm/@stoplight/[email protected] (t) upgrade to: > 4.14.1

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

@amaan-lob amaan-lob merged commit 1e5ed0d into main Mar 6, 2024
4 of 5 checks passed
@amaan-lob amaan-lob deleted the MI-86-update-qr-codes-in-campaigns branch March 6, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants