semantic checking of configuration files
Submitted by Kristof Szabados
Link to original bug (#568440)
Description
In the designer it should be possible to do semantic checking on configuration files, when the project contains both the configuration file to check and the source code of the modules it is used to configure.
In such a setup the already existing syntactic and semantic analyzer of the Designer should have all semantic information from the source code. It as also able to check the syntactic structure of the configuration files.
By adding semantic checking for the values in these configuration files, users would be able to detect if there is something wrong with their configuration file, that would prevent it from properly driving the execution ... during editing of the configuration file. It would also be possible to notify the user on the need of updating configuration files, when the modules they are configuring change in way to require it (for example some structured type is extended by an additional field)
Version: 7.1.0