-
Notifications
You must be signed in to change notification settings - Fork 209
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
Temporarily revert the Telemetry feature #515
Comments
I can remove dependency, and make sure that vscode-yaml will work without vscode-commons. |
Signed-off-by: Yevhen Vydolob <yvydolob@redhat.com>
* #515 remove telemetry Signed-off-by: Yevhen Vydolob <yvydolob@redhat.com> * update readme, remove installation of commons ext Signed-off-by: Yevhen Vydolob <yvydolob@redhat.com>
Telemetry will be back! |
SpyWare, uninstalled... |
@spirillen VS Code implements telemetry collection by default, you have to explicitly opt-out. And vscode-yaml is currently not implementing telemetry collection. |
Is your enhancement related to a problem? Please describe.
The vscode-commons dependency irks some users.
Describe the solution you would like
Before the latest release is fully rolled out, we should revert the change ASAP and try to find an alternative to the currently correct technical solution.
Describe alternatives you have considered
Simply removing the vscode-commons dependency might cause some runtime errors, it seems safer to rollback telemetry as a whole for now.
The text was updated successfully, but these errors were encountered: