Splitting out true_defaults for moduleConfig in export_config() #858
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The output of export_config() normally omits config values that have been set to false, because most protobuf config settings default to false anyway and therefore don't normally need to be set to false. But because some config values may default to true, PR #807 adjusted things that so that where specified "true default" settings have been set false for the node, then those specified settings will still export as false when using export_config().
The Issue
This adjustment adds a second "true_defaults" variable and set_missing_flags_false() call in relation to ModuleConfig, and sticks the mqtt default there.