-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat(dashboard): track selection of digest variables in autocomplete #8169
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
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Pull Request Overview
This PR adds telemetry tracking for digest variable selections in the dashboard's autocomplete features. Key changes include:
- Adding a new telemetry event (DIGEST_VARIABLE_SELECTED) in telemetry utilities.
- Modifying autocomplete source functions in liquid-autocomplete.ts and control-input.tsx to include telemetry tracking via a track callback.
- Integrating telemetry tracking into the MailyVariablesListView component in the email workflow editor.
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| apps/dashboard/src/utils/telemetry.ts | Added new telemetry event for digest variable selection |
| apps/dashboard/src/utils/liquid-autocomplete.ts | Updated autocomplete source to track digest variable selections and include a new telemetry callback |
| apps/dashboard/src/components/workflow-editor/steps/email/views/maily-variables-list-view.tsx | Integrated telemetry tracking for digest variable selection upon item selection |
| apps/dashboard/src/components/primitives/control-input/control-input.tsx | Passed telemetry track callback to autocomplete source function |
Comments suppressed due to low confidence (1)
apps/dashboard/src/components/workflow-editor/steps/email/views/maily-variables-list-view.tsx:78
- [nitpick] Consider using a consistent payload key (e.g., 'variable' instead of 'type') for the DIGEST_VARIABLE_SELECTED event to maintain consistency across telemetry calls.
track(TelemetryEvent.DIGEST_VARIABLE_SELECTED, { type: item.name, });
| track(TelemetryEvent.DIGEST_VARIABLE_SELECTED, { | ||
| type: item.name, | ||
| }); |
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.
Is it possible to have a generic "Variable Selected" event and pass the name as a pram?
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.
Yes, do we want to track all the variables including payload, subscriber etc
or just the digest ones for now?
d33bf92 to
110c46c
Compare
What changed? Why was the change needed?
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer