By including this small addition, the script will look for a file called config.yml located in the same directory as the open AI file. The current system already has a system to output settings to such a file with the includeInConfigFile setting.
Settings will now be loaded (in order from least to the most precedence):
A settings block located inside the AI file (generated by the script)
If no settings block is found inside the AI file, the value created in the block will also follow the same order of precedence (values in config.yml will overwrite the base settings).
This isn't a direct fix to #86, but it can potentially help make the script's configuration more robust.
By including this small addition, the script will look for a file called
config.yml
located in the same directory as the open AI file. The current system already has a system to output settings to such a file with theincludeInConfigFile
setting.Settings will now be loaded (in order from least to the most precedence):
defaultBaseSettings
/nytBaseSettings
config.yml
located in the same directoryIf no settings block is found inside the AI file, the value created in the block will also follow the same order of precedence (values in
config.yml
will overwrite the base settings).This isn't a direct fix to #86, but it can potentially help make the script's configuration more robust.