Change amp-analytics triggers from arrays to objects. #1193
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
|
LGTM |
cramforce
added a commit
that referenced
this pull request
Dec 18, 2015
Change amp-analytics triggers from arrays to objects.
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.
This changes how amp-analytics triggers are configured. Instead of specifying triggers as an array of objects, triggers are now specified as an object of objects.
This change was made because the way we merge configuration objects (built-in + vendor + inline + remote) is not effective for arrays.
The key for each trigger is an id string, used only when merging triggers from multiple configs (e.g. to override a inline trigger with a remote trigger.)