Don't use starting period to identify files to be deleted

Created on 27 September 2023, over 1 year ago
Updated 28 September 2023, over 1 year ago

Problem/Motivation

To identify config files that have been deleted, config_auto_export adds a period to the beginning of the file. This hides the files on most systems unless you specifically look for hidden files, and doesn't clearly identify the files as to be deleted.

Proposed resolution

Add "delete!" to the start of filenames that should be deleted. This will let users know what will happen to these files, and the exclamation point will prevent name conflicts with config from modules with names that start with "delete."

Remaining tasks

TBD

API changes

Files that will be deleted will no longer begin with periods.

✨ Feature request
Status

Active

Version

2.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States charginghawk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @charginghawk
  • πŸ‡ΊπŸ‡ΈUnited States charginghawk
  • πŸ‡©πŸ‡ͺGermany jurgenhaas Gottmadingen

    Thanks for suggesting this new feature. I wonder what should be wrong with "hidden" files due to their leading period in the filename. The exported files are not supposed to be processed by any human, but by some process that's doing "the right thing" with them. And such processes shouldn't care about the OS display policy of such files. Or am I missing a use case where this is still important?

    Having said that, using a different prefix could be implemented, but only as a configurable option with the current prefix, i.e. the period, as the default value. If anyone wanted to provide a merge request with such an implementation, I'd be happy to review and test this.

Production build 0.71.5 2024