-
Notifications
You must be signed in to change notification settings - Fork 101
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
Parsing a dubious JavaScript/JSON file #292
Comments
Strictly speaking, this isn't valid JSON--escape ( Whether or not we want to support passing this anyway I'd another question. I would be open to it, perhaps with an additional keyword argument (e.g., (You also might want to check out JSON3.jl) |
Thanks! A less strict option is always nice for the users, particularly when working on the fringes of the standards (talk to anyone working with Markdown...!). I get a similar-ish problem with JSON3.jl (albeit with a different file):
so I'll stay with LazyJSON for working with my malformed stuff, for now. |
I was deep in a rabbit hole trying to parse a JavaScript file that defined a JSON object. I found an easy way to reproduce it on a mac:
JSON.jl complains about a backslashed
'
:I thought at first that this may well be the correct thing to do. But when I tried LazyJSON, it parsed without errors, which made me think that it might be OK. I spent a few minutes searching the internet but couldn't work out whether a
\'
was OK or not...So I'll let you decide if this is a bug! :)
The text was updated successfully, but these errors were encountered: