-
Notifications
You must be signed in to change notification settings - Fork 62
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
feat(tree-explorer): add treeview telemetry and refactor to use a more standardized format VSCODE-651 #891
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Alena Khineika <alena.khineika@mongodb.com>
…nto gagik/add-playground-buttons
…nto gagik/add-icons
…agik/add-playground-buttons
gagik
commented
Nov 29, 2024
const commandPrefix = command ? `/${command} ` : ''; | ||
const query = `@MongoDB ${commandPrefix}${message}`; | ||
|
||
if (telemetry) { |
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 an example of it might be nice to structure tracking in other functions as some hot-pluggable thing.
addaleax
reviewed
Nov 30, 2024
gagik
force-pushed
the
gagik/add-telemetry-to-tree-view-buttons
branch
from
December 2, 2024 12:55
95bb2ee
to
68255cf
Compare
gagik
changed the title
feat: refactor telemetry to use a more standardized format VSCODE-651
feat(tree-view): refactor telemetry to use a more standardized format VSCODE-651
Dec 3, 2024
gagik
changed the title
feat(tree-view): refactor telemetry to use a more standardized format VSCODE-651
feat(tree-view): add treeview telemetry and refactor to use a more standardized format VSCODE-651
Dec 3, 2024
…vscode into gagik/add-telemetry-to-tree-view-buttons
gagik
changed the title
feat(tree-view): add treeview telemetry and refactor to use a more standardized format VSCODE-651
feat(tree-explorer): add treeview telemetry and refactor to use a more standardized format VSCODE-651
Dec 4, 2024
…vscode into gagik/add-telemetry-to-tree-view-buttons
…lemetry-to-tree-view-buttons
…lemetry-to-tree-view-buttons
alenakhineika
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Built on top of #890
Makes some minor quality of life improvements to our current telemetry setup, especially for
sendMessageToParticipant
.telemetry
field insendMessageToParticipant
(ideally a structure we could use in other places in the future?), which is meant to be a scalable structure for us to pass different arguments to functions we want to track without messing with our objects and too much manual work.command
field in various telemetry functions stricter; introduce and cleanup some types to better fit this. Right now we are not keeping a good track of what we call acommand
when sending telemetry, so this is hoping to document this better with types.Copilot
prefix in places where it may be redundant or not match its property type.Let me know what you think; this was mainly me a result of me trying to understand & document our current setup better, would be happy to adjust accordingly 🙂