Skip to content

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

Open
@jswalden

Description

@jswalden

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementNew feature or requestarea/import-exportRelated to the import/export processes.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions