-
Notifications
You must be signed in to change notification settings - Fork 15
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
Another comment oddity #26
Comments
thanks for reporting, the problem was with the |
Again, thanks for the rapid fix, but found yet another one. I can share our full default config file if it helps? key: {
# //
name: {
name: value
}
} Any URL in a comment before a { ... } encodes object causes an error - I will assume it's the '//' being seen as a comment as well and getting something out of sync. I have not checked what happens for /* ... */ inside # or // prefixed single lines, but I am guessing it's going to have similar issues... |
Yep, this also fails: key: {
# /* this is not ok */
name: {
name: value
}
} |
Thanks for the rapid fix of #25
I am trying to support in-the-field config files, so I have to test against messy files.
In this case:
generates:
removing the second comment - when it precedes a
{ ... }
fixes it.The text was updated successfully, but these errors were encountered: