Due tu the enum binding of properties in our config class, the resulting config-object in the textfile does contain entries to unused parameters even though the section hasn't been activated nor used.
This is somewhat confusing and should be changed.
A solution would be to override the default behaviour of the json serializer so that it doesn't include entries of sections which aren't toogled.
Due tu the enum binding of properties in our config class, the resulting config-object in the textfile does contain entries to unused parameters even though the section hasn't been activated nor used.
This is somewhat confusing and should be changed.
A solution would be to override the default behaviour of the json serializer so that it doesn't include entries of sections which aren't toogled.