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

Expose common folder paths: user directory, user desktop, user downloads #144

Closed
latman-oliveai opened this issue May 4, 2021 · 7 comments

Comments

@latman-oliveai
Copy link
Contributor

We want to save new files into the user's downloads folder. But, the directory location is operating system dependent, and the loop isn't aware of the running user to locate their user directory.

@cshields-oliveai
Copy link
Contributor

Hello @latman-oliveai - Thanks for opening this issue.

In version 3.0.0-beta.1 of the LDK, the Filesystem aptitude has a join function that can take filepath segments, and return a string representing a filepath that is aware of the users operating system.

Here is the documentation for that function.

I believe this would solve your issue. Let us know.

@latman-oliveai
Copy link
Contributor Author

I loved seeing that just a few minutes ago. But I don't actually know where the user directory is, what operating system the loop is running on, and who the logged-in user is, so it would be hard to build the paths to get to the current user's desktop.

@cshields-oliveai
Copy link
Contributor

Got it - I will mark this as an enhancement.

We do need to ensure security for the end user, and reporting to the Loop some of those things may be a violation. This one will take some discussion. Let me get some input from the teams and figure out priority for you.

Thanks for expanding on this.

@cshields-oliveai cshields-oliveai self-assigned this May 4, 2021
@cshields-oliveai
Copy link
Contributor

@latman-oliveai - The team feels that this is a good idea, and would like to add it to the roadmap. We have created a new internal task for this: SIDE-2209. We will update this Github Issue when we complete the feature.

@latman-oliveai
Copy link
Contributor Author

Great thanks!

@CandiceCLB
Copy link

Updating ticket number for tracking: HELPS-166

@BrettMugglinOlive
Copy link
Contributor

I'm going to go ahead and close this thread. Please feel free to reopen if you feel that the problem still doesn't have an adequate workaround through using the System aptitude to determine OS, and change behavior based on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants