Skip to content
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

Feature request: get file path after copying to Downloads folder #11

Open
v21 opened this issue Feb 7, 2025 · 2 comments
Open

Feature request: get file path after copying to Downloads folder #11

v21 opened this issue Feb 7, 2025 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@v21
Copy link

v21 commented Feb 7, 2025

Hiya - thanks for the plugin, this looks great. Right now, the flow I have in my app is that I attempt to share the file, and let the user choose what to do with it from the share picker. I think it would make more sense to copy to the Downloads folder (using this plugin!) and then offer the share prompt. However, to do this, I need to get a reference or a file path to the now-saved file within the Downloads folder. But alas, this plugin has the nice helpful feature of renaming files in case of a filename conflict. So if the file is saved multiple times, the share dialog would share the first version repeatedly. Would it be possible to return the copied file path instead of just a boolean success value?

@UnluckyY1 UnluckyY1 added the enhancement New feature or request label Feb 9, 2025
@UnluckyY1 UnluckyY1 self-assigned this Feb 9, 2025
@UnluckyY1
Copy link
Owner

Hi There- I completely agree this is a valuable improvement. I’ll work on updating the plugin to return the final file path (or URI) instead of a boolean...I’ll aim to implement this in the next few weeks.
Cheers!

@v21
Copy link
Author

v21 commented Feb 9, 2025

Ah, thank you so much! No rush!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants