feat: Enhance analytics functionality and improve telemetry logging - #84
Merged
Conversation
…feat/analytics
This file contains hidden or 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
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 pull request updates the application to version 1.0.2 and introduces improvements to analytics tracking and configuration persistence. The most important changes are grouped below:
Analytics Configuration and Persistence:
AnalyticsServicenow reads the user's analytics preference from ananalytics.jsonfile in the app data directory at startup, ensuring analytics are enabled or disabled based on persisted user choice.analytics.json, making the setting persistent across app restarts.Analytics Event Dispatching:
app_startedevent, and logs clearly whether analytics are on or off.Version Bump:
1.0.1to1.0.2inpackage.json,bridge/package.json, andsrc-tauri/tauri.conf.json. [1] [2] [3]