Revise mailchimp export code to apply new defaults #4276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ldodds
changed the title
ldodds
deleted the
4792-revise-mailchimp-export-code-to-apply-new-defaults
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revises the code that creates improved CSV files for importing into Mailchimp, so that it correctly adds in default interests. We will use this when doing the initial imports. The behaviour is optional so we can still run this code after the initial user import and ensure that we preserve interests.
The PR also removes some old code that was mapping between old Mailchimp fields and the new schema. The old fields have been removed from Mailchimp so we no longer need the code and specs.