-
Notifications
You must be signed in to change notification settings - Fork 0
feat: reviewing state change events #39
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
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.
Looks good to me. I think. If we can test it locally and see events propagated, we're golden.
We have repeat os/ide detection logic, I have extracted it to a helper class.
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.
Made some changes, I need clarification on this one if statement, I think its too convoluted
Caution
This PR was entirely done using Cursor + Codex. Review with care. 🙈
Problem
After analysis, it was discovered that state change telemetry events were not being properly emitted by the IntelliJ extension. The extension was missing critical telemetry tracking for repository, pull request, and branch state transitions, which are essential for analytics and monitoring user behavior across different IDE extensions.
Solution
This PR implements comprehensive telemetry state change tracking to match the VS Code extension behavior and includes several improvements for better IDE and OS parameter normalization.
Changes Made
🔧 Telemetry State Change Events
Missing components