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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since other code may interoperate with the dataLayer, would anyone object to adding a prepended 'ng-' or 'nglytics-' to the values we're setting for the event property when we push it in? The logic here is pretty much the same as Angular prescribes in their docs for Directive naming - at some future point, Google or a 3rd party may introduce an event that would collide with a too-generic event name.
Again, the idea being that someone else could set the 'label' property, which could be accidentally inherited by an event angulartics fires later on down the line, leading to some confusing and hard to debug issues.
Any objections? I can put together a PR with fixed docs etc.
The text was updated successfully, but these errors were encountered:
Since other code may interoperate with the dataLayer, would anyone object to adding a prepended 'ng-' or 'nglytics-' to the values we're setting for the event property when we push it in? The logic here is pretty much the same as Angular prescribes in their docs for Directive naming - at some future point, Google or a 3rd party may introduce an event that would collide with a too-generic event name.
E.g.:
becomes
One further step we could take would be to namespace all of our properties, too, like so:
Again, the idea being that someone else could set the 'label' property, which could be accidentally inherited by an event angulartics fires later on down the line, leading to some confusing and hard to debug issues.
Any objections? I can put together a PR with fixed docs etc.
The text was updated successfully, but these errors were encountered: