deej.exe uses file watch monitor to detect changes in config.yaml, but this file watch monitor DOES NOT use a full path but only the file name. Hence, when ANY OTHER config.yaml file is touched ANYWHERE on the machine, deej.exe issues a reload.
I started noticing notifications about "Configuration reloaded!" even though I'm not touching deej folder, but I am working on some other projects that, accidentally, use the SAME NAMED file in their folders.
This can be solved either by changing the file watch monitor to include the full path to config.yaml, if possible, or simply by changing the filename from config.yaml to deej_config.yaml in the source code, thus making this filename somewhat more unique.
deej.exe uses file watch monitor to detect changes in config.yaml, but this file watch monitor DOES NOT use a full path but only the file name. Hence, when ANY OTHER config.yaml file is touched ANYWHERE on the machine, deej.exe issues a reload.
I started noticing notifications about "Configuration reloaded!" even though I'm not touching deej folder, but I am working on some other projects that, accidentally, use the SAME NAMED file in their folders.
This can be solved either by changing the file watch monitor to include the full path to config.yaml, if possible, or simply by changing the filename from config.yaml to deej_config.yaml in the source code, thus making this filename somewhat more unique.
Thanks.