-
Notifications
You must be signed in to change notification settings - Fork 175
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
Add support for custom file names #772
Comments
Hi, Yes we removed dynamic file names for exported csv/tsv. Code responsible for this was convoluted and unreliable. Names weren’t good either. For sure we’re not going to bring it back. But, we’re open to suggestions how file names should look. Feel free to submit some reasonable schemes and we could discuss if they’re feasible to implement. Cheers! |
Hi, Thanks for the response. Could there be a configurable template for the file name so that user doesnt have to specify it every time? For our use case, we'd like something like |
I don't think we want to add filename template to config.
Sounds doable, can I get some feedback from others? |
@adrianmroz the generated file name would be good. is there a unique |
Nope. I was thinking that would be data cube id. |
@aagoath @kottameister What do you think about this: |
@adrianmroz this looks exactly what we were looking for. thanks. |
Hi,
I noticed that Export to CSV doesn’t use a descriptive name in the file name any more, but simply turnilo-export.csv. It might be related to #747. Would it be possible to support encoding without hardcoding the file name?
Thanks
The text was updated successfully, but these errors were encountered: