bitfocus
feat: allow custom export file name
This adds the a config field to customize export file names to aid with organization of config exports. It partially addresses https://github.com/bitfocus/companion/issues/3075
@bryce-seifert did you try to investigate variable parsing as part of adding this field?
I did look at parsing, but was not sure how to get that functional. If you have any pointers or ideas, happy to investigate more. I'm curious how much variables would be used, too, since this modal is ephemeral, so you'd have to enter variables every time. Perhaps that issues is solved outside of this modal, but not sure where best to do it
@bryce-seifert I hear you on attempting to figure out how to handle and being confused. That's why I asked and got an appropriate response. To properly implement to the issue referenced, we probably need a default_export_filename userconfig value with a default just as that user prescribes.
I like what you're doing here, as its attempting to respond to #3075. I get its not ephemeral, but I'd challenge you to reach beyond that as I've described and reach out to me or Julian in Slack if you need help or inspiration.
@krocheck I have worked on adding the default_export_filename to the user config that allows for variables, as well as added the ability to override the default and use variables in all of the export modals. Let me know what suggestions you have on the implementation
Here's the new user config, which defaults to a similar format as the current export defaults
Here's the file name parameter in the custom export modal
And the file name parameter in the other export modal used for pages and triggers