[bug] Non-empty default values for child config components override parent configs
namolnad opened this issue · comments
Describe the bug
Default values for section infos (possibly other areas) override parent configs even if there are specific values set there. This was noticed with a private config files overriding the section infos from the regular config file even though section_infos was not a present key in the private config. This may be happening for other non-empty default values within configs.
To Reproduce
Steps to reproduce the behavior:
- Create a private config with only users as it's contents
- Have a regular config file which has your custom
section_infos
- See the
section_infos
are not your custom values, but the defaults when you runfinch compare
Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
- OS: macOS
- Version 0.0.21