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

Respect the new core.telemetryConsent configuration option #1179

Closed
1 task done
lee-dohm opened this issue Sep 5, 2016 · 3 comments
Closed
1 task done

Respect the new core.telemetryConsent configuration option #1179

lee-dohm opened this issue Sep 5, 2016 · 3 comments

Comments

@lee-dohm
Copy link

lee-dohm commented Sep 5, 2016

Description

In Atom v1.11.0-beta0 a new Telemetry Consent system was introduced. The user's decision is stored at core.telemetryConsent. The three possible values are undecided, no and limited. The intent is that consent is given if and only if limited is chosen. The atom-beautify package should respect this decision also.

Expected Results

When core.telemetryConsent is set to undecided or no, atom-beautify does not collect any data on the user's behavior or use of the package.

Checklist

  • N/A - I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
  • N/A - I have reloaded (or restarted) Atom to ensure it is not a caching issue
  • Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
    so I know this is not a duplicate issue
  • N/A - Generated debugging information and added link for debug.md Gist to this issue
@Glavin001
Copy link
Owner

Glad to see this built-in to Atom! If someone does not submit a Pull Request by this upcoming weekend, I'll implement it and publish a release. Thanks for letting me know!

@Glavin001
Copy link
Owner

Published to v0.29.23

@Glavin001
Copy link
Owner

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants