Maybe we should default to false since this is the current behavior, and it might be unexpected that a tag field in the data would update the tag on the URL
@mostlyjason This is just the documentation. By default it appears that the mutableTags property on the tracker will be undefined
});
```
If mutable tags are enabled, any log object passed with a 'tag' key will overwrite the previous tags.
Setup Proxy for Ad blockers
----------
You can proxy the requests from your own domain if the script or its requests are blocked by Ad blockers. To do this, you need to perform following steps
It seems this won't work if they initialize the library with mutableTags=false and tag=some value. We want to allow it to set during initialization.
setInputUrl(tracker);
}
}
functionsetMutableTags(tracker){
tracker.mutableTags=true;
}
functionsetDomainProxy(tracker,useDomainProxy){
tracker.useDomainProxy=useDomainProxy;
@@ -118,6 +125,10 @@
if(data.sendConsoleErrors !== undefined){
setSendConsoleError(self,data.sendConsoleErrors);
}
if(data.mutableTags){
setMutableTags(self);
}
if(data.tag){
setTag(self,data.tag);
ProTip!
Use n and p to navigate between commits in a pull request.
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.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
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
Allow different tags on each log statement #35
Allow different tags on each log statement #35
Changes from all commits
d49a02f5e307edFile filter...
Jump to…
mostlyjasonDec 8, 2015
Contributor
Maybe we should default to false since this is the current behavior, and it might be unexpected that a tag field in the data would update the tag on the URL
tgrrttApr 12, 2017
@mostlyjason This is just the documentation. By default it appears that the
mutableTagsproperty on the tracker will beundefinedmostlyjasonDec 8, 2015
Contributor
It seems this won't work if they initialize the library with mutableTags=false and tag=some value. We want to allow it to set during initialization.