-
Notifications
You must be signed in to change notification settings - Fork 361
[Analytics] Using the actual widgetId on our widget rendering events. #3027
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
Conversation
…et rendering events.
🗄️ Schema Change: No Changes ✅ |
🛠️ Item Splitting: No Changes ✅ |
|
Size Change: -3 B (0%) Total Size: 498 kB
ℹ️ View Unchanged
|
… rendering analytics events to use accurate widgetIds
jeremywiebe
left a comment
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.
Thanks for fixing these up!
…ctive graph." This reverts commit a182fcc.
…w bummer but gotta be done.
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (8f014c1) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR3027If you are working in Khan Academy's frontend, you can run the below command. ./dev/tools/bump_perseus_version.ts -t PR3027If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -t PR3027 |
Summary:
Updating our rendering analytics events to use the actual widgetId.
Issue: LEMS-XXXX
Test plan: