-
Notifications
You must be signed in to change notification settings - Fork 43
Setting to disable analytics #847
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
Setting to disable analytics #847
Conversation
📦 build.zip [updated at Sep 9, 11:30:09 AM UTC] |
abd89c8
to
0fe2a24
Compare
if (!explicitly) { | ||
return; | ||
} |
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.
should this condition come first?
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.
Yes, this is fair. My only logic was to place this settings check as same as possible everywhere to simplify the usage
const preferences = await globalPreferences.getPreferences(); | ||
if (!preferences.analyticsEnabled) { | ||
return; | ||
} |
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 check is repeated over and over. Do you think we can create a helper that abstracts this?
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.
Discussed and decided to keep it this way for now
No description provided.