Add Telemetry Opt-Out Feature - Fixes #62 #65
Closed
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
gardner
reviewed
Oct 23, 2023
gardner
reviewed
Oct 23, 2023
|
can any of the maintainers please have a look at this PR and let me know if the changes can be merged or does it require any sort of modifications? |
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.
This PR fixes #62 by adding a feature that allows developers to opt-out of telemetry. The changes include modifications to the postinstall.js and jest-config.js files, enabling the use of the PYTHAGORA_TELEMETRY_ENABLED environment variable to control telemetry. Developers can set this variable to false to opt-out of telemetry when running the script or tests.
This feature provides more flexibility to developers using the Pythagora tool by respecting their preference for telemetry data collection.