Skip to content
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: residual space after section causes bad parsing #123

Merged
merged 1 commit into from Apr 12, 2023

Conversation

Nautigsam
Copy link
Contributor

Any character left on a line after a section should be ignored.

If we try to parse this input :

; there is a space character left at the end of the next line
[section] 
key=value

I get the following result:

{
  "[section]": true
  key: "value"
}

Instead, I want the section to be correctly parsed.

@Nautigsam
Copy link
Contributor Author

🆙 I rebased the PR on main branch.

@wraithgar
Copy link
Member

Rebased in #203 to let CI run

Any character left on a line after a section should be ignored.
@Nautigsam Nautigsam requested a review from a team as a code owner April 12, 2023 14:33
@wraithgar wraithgar merged commit 5b5c9b7 into npm:main Apr 12, 2023
23 checks passed
@github-actions github-actions bot mentioned this pull request Apr 12, 2023
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.

None yet

2 participants