-
Notifications
You must be signed in to change notification settings - Fork 321
Reworked app update flow #3960
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
base: main
Are you sure you want to change the base?
Reworked app update flow #3960
Conversation
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 PR has more frontend than backend code, but both LGTM.
I just have a couple nitpicks I'd like to share below.
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.
Thanks!
would be good to double check my latest changes didn't break functionality, requested another review from @IMB11 Feel free to queue for merge if it looks good to you |
Out of interest, what's blocking this? |
e8b95d8
to
a6fc14c
Compare
Signed-off-by: Cal H. <hendersoncal117@gmail.com>
…wnloads if you're on a metered network
# Conflicts: # apps/app-frontend/src/App.vue # apps/app-frontend/src/components/ui/ProgressBar.vue # apps/app-frontend/src/components/ui/modal/ModalWrapper.vue # apps/app-frontend/src/helpers/settings.ts # apps/app-frontend/src/helpers/utils.js # apps/app/package.json # apps/frontend/package.json # apps/frontend/src/components/ui/servers/PlatformMrpackModal.vue # packages/app-lib/Cargo.toml # packages/ui/src/components/modal/NewModal.vue
# Conflicts: # packages/blog/compiled/index.ts
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.
The backend side looks good to me after all the recent additions, thanks!
As a side note, I think we should simplify the handling of metered connections and their interaction with the automatic update downloads option. Instead of the current approach, we could offer a single setting with three choices: always download, only download over unmetered connections, and always task, as suggested by @Gaming32 when we had a chat over the matter over Slack. Any initial popup would then be limited to let users choose their preferred default, at most. That way, we'd gracefully handle cases where users switch networks, without making them face the unexpected extra costs or missed updates that a more binary approach of either always downloading automatically or never doing it would.
The old app updater automatically installed new updates immediately on startup with no user involvement or consent. This reworks it to have a new modal that asks whether the user would like to update now, update on next restart, or skip this update.
Closes DEV-128
Closes DEV-229