Choose custom download location for attach@store objects

[horsto]

Feature Request

This is a follow-up of a discussion with @ttngu207 on Slack.
For attach@store logic, the files are downloaded into the current working directory upon fetch(). This has the advantage that the user can call the file path directly, but it causes a lot of cluttered files to be saved in a potentially suboptimal location on the drive.

Requirements

The download path for attach@store objects should be configurable and the file path should be updated automatically upon fetching to reflect that user-configured location.

[christoph-blessing]

Does Table().fetch(download_path="mypath") not do what you are proposing?

[horsto]

Oh I did not know that existed! Thanks for pointing to that.

Ok, then I have a follow-up question, whether that download_path variable could somehow be made configurable globally so it does not have to be called in every fetch.