Skip to content

boolean keys do not get sanitised from the \n#77

Merged
unknwon merged 6 commits into
go-ini:masterfrom
zeph:master
Jan 22, 2017
Merged

boolean keys do not get sanitised from the \n#77
unknwon merged 6 commits into
go-ini:masterfrom
zeph:master

Conversation

@zeph

@zeph zeph commented Dec 16, 2016

Copy link
Copy Markdown

I would have loved to provide as well a patch...
I'll try, but maybe someone else is faster than me

here is a unit test that properly isolates the problem

@zeph zeph changed the title a boolean key gets a trailing \n if followed by a #comment boolean keys do not get sanitised from the \n Dec 20, 2016
@zeph

zeph commented Dec 20, 2016

Copy link
Copy Markdown
Author

patch provided!!! :)

zeph pushed a commit to zeph/goad that referenced this pull request Dec 21, 2016
as go-ini/ini has not yet merged my patch on booleanKeys (required to enable/disable regions)
 - go-ini/ini#77
 - go-ini/ini#78
@unknwon

unknwon commented Dec 22, 2016

Copy link
Copy Markdown
Member

Just one comment and the conflict, otherwise LGTM.

@zeph

zeph commented Dec 22, 2016

Copy link
Copy Markdown
Author

@unknwon rebased and fixed

@zeph

zeph commented Jan 11, 2017

Copy link
Copy Markdown
Author

@unknwon is there anything else I need to provide?

@prawnsalad

Copy link
Copy Markdown

Will this be getting merged in? I'm getting hit with this issue :(

@unknwon unknwon merged commit 2ba7300 into go-ini:master Jan 22, 2017
unknwon added a commit that referenced this pull request Jan 22, 2017
@zeph

zeph commented Jan 23, 2017

Copy link
Copy Markdown
Author

@prawnsalad seems it just got merged :) yay!

@prawnsalad

Copy link
Copy Markdown

Thanks!

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.

4 participants