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
when one wants to check WHERE segment.track was used one should use console.trace instead of console.log. Right now in debug mode all logs originate in the same line in angular-segment-analytics source which is not useful for finding a call with incorrect arguments)
when one wanted to use different logger than console (for example $log)
Suggested API:
if setDebug() is called with a boolean then console.log is used, if function is passed this function is used, or
setLogger(someFunction)
The text was updated successfully, but these errors were encountered:
I have 2 use cases where this might be useful:
when one wants to check WHERE
segment.track
was used one should useconsole.trace
instead ofconsole.log
. Right now in debug mode all logs originate in the same line inangular-segment-analytics
source which is not useful for finding a call with incorrect arguments)when one wanted to use different logger than
console
(for example $log)Suggested API:
setDebug()
is called with a boolean thenconsole.log
is used, if function is passed this function is used, orsetLogger(someFunction)
The text was updated successfully, but these errors were encountered: