You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
I have needed to maintain multiple different configurations on the same FC target.
In this use case having the craft_name within the Diff/Dump/Backup file names has been more helpful than target name when finding the correct configuration file(s) .
Describe the solution you'd like
Append "_craft_name" within output file names when not empty.
Because craft_name is contained within the file contents (if set) I can not think of any good reason this should not be the default option. However, if there is a good reason to set craft_name within config and not include craft_name in the file name maybe we should add a user option to the configurator?
Other information
For now I have been appending craft_name manually in order to save time and prevent error when searching the file contents to find/re-load the correct config.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
I have needed to maintain multiple different configurations on the same FC target.
In this use case having the craft_name within the Diff/Dump/Backup file names has been more helpful than target name when finding the correct configuration file(s) .
Describe the solution you'd like
Append "_craft_name" within output file names when not empty.
eg:
BTFL_cli_backup_20231117_123456_BETAFLIGHTF4**_craft_name**.txt
Describe alternatives you've considered
Because craft_name is contained within the file contents (if set) I can not think of any good reason this should not be the default option. However, if there is a good reason to set craft_name within config and not include craft_name in the file name maybe we should add a user option to the configurator?
Other information
For now I have been appending craft_name manually in order to save time and prevent error when searching the file contents to find/re-load the correct config.
The text was updated successfully, but these errors were encountered: