(Yet another) comment issue

[pgalbavy-itrs]

Again, thanks for the rapid fix for the previous issue, 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...

(I have confirmed that # /* this is an embedded comment */ also triggers an error)

Originally posted by @pgalbavy-itrs in #26 (comment)