Cleaning input through the configure structures
- Private objects of the parsed configure structs.
- No friend classes to access private parameters directly.
- Access of the parameter structs using getter functions.
- Use
.at()
to access fields within the json so that it checks the fields actually exist.
Old Description: Accessing the config file outside of the config structures is error prone since default values are not handled properly. Therefore the access to the config file should be restricted to all config structures but no other entities within the BSL6D code.
The following discussion from !133 (merged) should be addressed:
-
@nilsch started a discussion: (+2 comments)
Should we not create an rhs config structure for this comparison?