Valid json doesn't work in the json editor about ravendb HOT 4 CLOSED

Keys in JSON must be double quoted according to the spec. This isn't valid JSON.
See: http://awurl.com/mbsj9bz81#first_awesome_highlight

I can handle it if you want, just do a replace on single quotes, but that could have unintended consequences (i.e. replacing intentional single quotes)

from ravendb.

I know that they should, but the fact is that most people don't behave in this manner
I don't really know why that decision was made, but I think we need to support it.

from ravendb.

I don't really know how to do this without potentially impacting valid JSON like the following:

{ "name" : "ayende's name" }

I can replace single quotes with double quotes, but that will modify that valid JSON. We can write our own JSON parser, but I don't know of any parsers that will accept malformed JSON and smartly (this is ambiguous) parse it.

from ravendb.

Yeah, good point.
I almost want to use eval for this, but I will resist.
Okay,

from ravendb.