What problem should be fixed?
When configured with
AllowNestedValues: true, the parser attempts to parse values "nested" under a key, AWS-style. To trigger this behavior, the parent key must have an empty value, and child keys must be indented. However, if the next value is in a different section, it cannot be a nested value, but the parser can treat it as such anyways. As an example:
[section] key1 = value1 key2 = [section2] key3 = value3
Before this PR,
key3 is treated as a nested value under
section2 has no keys.
Have you added test cases to catch the problem?
Yes, I've added tests that cover the issue and fail on the current tip of