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

[BUG] The "Default Export File Name" setting is omitted in configuration exports (and is reset during importing) #3276

Open
2 tasks done
jswalden opened this issue Feb 9, 2025 · 2 comments
Labels
BUG Something isn't working

Comments

@jswalden
Copy link
Contributor

jswalden commented Feb 9, 2025

Is this a bug in companion itself or a module?

  • I believe this to be a bug in companion

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

The setting to set the default config-export filename isn't saved in those same exports.

That's maybe annoying, but it's not the worst thing in the world on its own.

What makes it much worse is that importing an exported configuration resets that default filename setting. So any time you make a mistake and use your backup to revert, the next time you export you have to set the very thing that was supposed to be a default...which makes the setting itself kind of useless.

I might try to fix this. OTOH last time I tried looking at the export/import code, to try fixing #2688, I got confused by seemingly snarly code in it, so I easily might not, too.

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

Additional context

No response

@jswalden jswalden added the BUG Something isn't working label Feb 9, 2025
@jswalden
Copy link
Contributor Author

So there's plainly some vague idea of including userconfig details (settings) in exports in the code. But it's just commented out -- as if it is believed to be undesirable to include any settings information (including this filename) -- or perhaps more to the point, all of it indiscriminately -- in exports.

// userconfig: true,

// userconfig: true,

{/* <div className="indent3">

It's intentional that UserConfigModel not be saved wholesale in exports or overwritten wholesale in imports. I can easily imagine justification for some of it, for example the HTTPS cert stuff probably at least would demand some opt-in. But I don't have the background to really understand the philosophy the code should embody: which settings would one reasonably want to export, which ones would one want to exclude, what the defaults should be, etc. And without that background, and presuming the undesirability of just bulling ahead to update the export format for exactly one setting, this seems beyond my capacity given my still-meager understanding of the project aims here.

@Julusian
Copy link
Member

There is a WIP PR related to this #2875

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants