Silent And Automatic Update Check #660
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
|
@ashitaprasad |
|
Which AI tool did you use to generate the code in this PR? |
|
I used codium windsurf to complete repetitive tasks and suggestions. I also verified the code manually after all of my commits. |
|
Resolve other open PR first. |
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.
PR Description
This PR implements the in-app update check feature for APIDash. The feature checks for the latest version of the application using the GitHub API and notifies users if an update is available. It supports update handling for Windows, Linux, Android, iOS and macOS platforms.
Also the update check is silent and it uses Isolates.
Related Issues
Checklist
mainbranch before making this PRflutter upgradeand verify)flutter test) and all tests are passingAdded/updated tests?
We encourage you to add relevant test cases.
I would add the tests when the current approach to solve the issue is finalized.
OS on which you have developed and tested the feature?