Skip to content

Conversation

@aligator
Copy link
Contributor

What problem should be fixed?

The problem in #241

Have you added test cases to catch the problem?

Yes, I added a test case for the case pointed out in the issue #241 by tevino.

@codecov
Copy link

codecov bot commented May 25, 2020

Codecov Report

Merging #242 into master will decrease coverage by 0.15%.
The diff coverage is 55.55%.

@@            Coverage Diff             @@
##           master     #242      +/-   ##
==========================================
- Coverage   86.41%   86.25%   -0.16%     
==========================================
  Files           9        9              
  Lines        1884     1885       +1     
==========================================
- Hits         1628     1626       -2     
- Misses        196      198       +2     
- Partials       60       61       +1     
Impacted Files Coverage Δ
struct.go 79.65% <55.55%> (-0.54%) ⬇️

Copy link
Member

@unknwon unknwon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

@aligator aligator requested a review from unknwon May 26, 2020 19:53
@unknwon unknwon changed the title bugfix #241: use the value from the correct section when using non unique sections in some special cases struct: correctly mapping non unique sections to slice field May 28, 2020
@unknwon unknwon merged commit 1fc6efb into go-ini:master May 28, 2020
@unknwon
Copy link
Member

unknwon commented May 28, 2020

New release tagged: https://github.com/go-ini/ini/releases/tag/v1.57.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants