-
Notifications
You must be signed in to change notification settings - Fork 556
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
Update telemetry format and rules #1624
Conversation
version: __VERSION__, | ||
lib_version: auth0.version | ||
}; | ||
const { auth0Client } = qs.parse(window.location.search.substr(1)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
won't this include anything on the query, not just the auth0Client query param?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is parsing the query string and getting only the auth0Client
key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I just see the destructuring 👍
@luisrudge - So ... before we merge this in, I think we should resolve the "telemetry on the ULP" question. As in ... should we just nuke telemetry when Lock/Auth0.js is used on our server? I tend to lean towards "yes" here. I'll post this internally for discussion 👍 |
Changes
Added new telemetry format
Testing