-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(web): include timestamp in download filename #5878
feat(web): include timestamp in download filename #5878
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.
Why can't we accept multiple download requests for the same type?
To avoid this behaviour : #5874 |
I can make it block based on the file name and not the download type |
How it will behave with 1 file 1.file.mov |
How it will behave with multiple files: Multiple.files.mov |
How it will behave with Album Download: Album.download.mov |
NOTE: |
web/src/lib/components/photos-page/actions/download-action.svelte
Outdated
Show resolved
Hide resolved
This is now covered : Screen.Recording.2023-12-20.at.18.10.02.mov |
Maybe as an option there is make save interface like for uploading? |
Hey @alextran1502 you have set this PR as draft. I am not planning to do any extra change. Shall it pass to ready for review ? |
This is trying to solve/fix some of the usability issues around file downloads, but we should probably try to address them directly.
|
Thanks @jrasm91 for your comment.
In which scenario do you think a user will trigger download twice for the same exact files ? (Before the current download is done)
The change that I am proposing is adding date to the download for example:
The current change will block downloading twice the same files while the download is not done, and if the user try to download s(he) will get a warning to let her/him know: |
In general, I'm for (1) improving user experience and (2) doing so with minimal code. I am good with the default archive name change as this helps with (1). I don't like the idea of showing a duplicate download message at all. It's an arbitrary limitation. So what if the user wants to start a second download immediately? If the user did not intend to download it again then you have a usability issue that should be fixed. Assuming it is fixed, the need for code to track duplicate downloads just becomes a maintenance burden or something that frustrates the user which has a legitimate reason for clicking it a second time. |
Hey @jrasm91, |
@jrasm91, I have updated the PR. |
The mobile tests have been a bit flaky lately so don't worry about that one. |
What do you think of adding a notification when the user clicks download? |
This is a suggestion to fix #5874.
~~ The current implementation block any multiple download for the same time (asset or archive), until the current download is done~~
My PR will block any multiple download for the same time (asset or archive), until the current download is done.User can download an archive and an asset at the same time, but never the same kind of download at the same time.This is can be improved if needed and you think is better, to block the download only based on file name. So users can download as many files as they want in parallel, as long they are not the same files.Here is how the current changes will looks like :https://github.com/immich-app/immich/assets/52571029/0875ff50-4dd7-4416-a232-a09a7f26a1e6This PR will :
For example :