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
The current solution of hardcoding the filename and directory name to settings.yml and settings folder is not ideal, as it can lead to conflicts if the same filename or directory name is already being used by other logics.
A better solution is to add two configuration fields, Config.file_name and Config.dir_name, which will allow users to specify their own filename and directory name. This will make it possible to avoid conflicts and it will also give users more flexibility in how they store their data.
Solution
Added two configuration fields:
Config.file_name for filename
Config.dir_name for directory name
The text was updated successfully, but these errors were encountered:
Problem
The current solution of hardcoding the filename and directory name to
settings.yml
andsettings
folder is not ideal, as it can lead to conflicts if the same filename or directory name is already being used by other logics.A better solution is to add two configuration fields,
Config.file_name
andConfig.dir_name
, which will allow users to specify their own filename and directory name. This will make it possible to avoid conflicts and it will also give users more flexibility in how they store their data.Solution
Added two configuration fields:
Config.file_name
for filenameConfig.dir_name
for directory nameThe text was updated successfully, but these errors were encountered: