-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix an issue where sections were not properly divided when parsing the config file #1216
Conversation
Hi, thanks for the contribution! Because we are still refining our external contribution process, those It would be nice to have a test that confirms this behavior is fixed, would you be able to add an entry to our parser test suite? If you have trouble or aren't interested in doing that, let me know and I can work on adding it. |
…e as default profile
Hi, thank you for reviewing PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the test. I confirmed it works and ran the extra CI in #1219, it all passed. Thanks for the contribution!
Quality Gate passedIssues Measures |
Hi, Thank you for your approval.
Can my PR be merged?
|
Yes, sorry I overlooked this. It should be available in tomorrow's release, v1.0.63. |
Issue #
Description of changes
When parsing sections in a config file, duplication between items with and without a section prefix is being removed. At this time, if different sections have the same name, a problem occurs where they are removed.
For example, the default profile is removed from the config file below.
It seems that the logic for verifying section duplication is based on before the config file supports various section types.
Therefore, we modified it to check the type of the section as well when removing duplicates.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.