Skip to content
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

Improve note about performance of commandExecuted handlers. #127

Merged
merged 1 commit into from Nov 2, 2020

Conversation

ellisonbg
Copy link
Contributor

Extensions are using the commandExecuted signal to observe user actions at a broad level (for telemetry for example). The previous comment was vague about when it is ok to use this signal. The new comment clarifies the underlying issue.

Extensions are using the `commandExecuted` signal to observe user actions at a broad level (for telemetry for example). The previous comment was vague about when it is ok to use this signal. The new comment clarifies the underlying issue.
Copy link
Contributor

@jasongrout jasongrout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@blink1073 blink1073 merged commit 2d64926 into master Nov 2, 2020
@vidartf vidartf deleted the ellisonbg-patch-1 branch November 9, 2020 15:54
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants