-
Notifications
You must be signed in to change notification settings - Fork 3
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
1550 confirm patch endpoint #1575
Conversation
✅ Deploy Preview for labs-zap ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
d9353fb
to
6648544
Compare
* @returns {object} | ||
*/ | ||
async update(environment: string, email: string, custom_fields: object) { | ||
var updated_custom_fields = Object.entries(custom_fields).reduce((acc, curr) => ({ ...acc, [`zap_${environment}_${curr[0]}`]: curr[1] }), {}) |
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.
Can we stick with let
or const
and camelCased variable/parameter names?
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.
Do you want me to update to let
and camelCase for the create
in here as well ?
Co-authored-by: David Hochbaum <[email protected]>
cd64fbb
to
f9755a1
Compare
Closes #1550
I tested it with the following request body in Postman:
and with a
zap_staging_id
pulled from Sendgrid contacts.