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.
While testing other items I noticed that the generate_config_includefile function will happily create an empty file if neither a user-provided file nor a default/fallback file is available.
But because the file is present but doesn't have any actual content, you end up with a slightly obfuscated compiler error about missing symbols rather than an indication that the expected config file is empty.
Describe the solution you'd like
The function should trigger an error and inform the user that there was no file to use, rather than generating an empty file. It is a misconfiguration, so it should be corrected.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Calling it an "enhancement" as it isn't strictly broken - more of a reporting/informational concern. Could be argued to be a bug though, as the build should inform the user if their config is broken.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jul 9, 2020
Is your feature request related to a problem? Please describe.
While testing other items I noticed that the
generate_config_includefile
function will happily create an empty file if neither a user-provided file nor a default/fallback file is available.But because the file is present but doesn't have any actual content, you end up with a slightly obfuscated compiler error about missing symbols rather than an indication that the expected config file is empty.
Describe the solution you'd like
The function should trigger an error and inform the user that there was no file to use, rather than generating an empty file. It is a misconfiguration, so it should be corrected.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: