Update to work with multiple Campaign Monitor accounts (API keys) #3
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.
Previously,
List
,Client
andCampaign
objects generated a newCampaignMonitor
client object in theirinitialize
methods. This defaults to using the system-wideCAMPAIGN_MONITOR_API_KEY
constant, which prevents using multiple API keys if you have to add data to two separate Campaign Monitor accounts in your app.This change allows a pre-instantiated
CampaignMonitor
object to be passed intoList
,Client
andCampaign
, thus making working with multiple CM accounts trivial.