From 73f4dadde59df22f226e3ed0ab73ffb937c091a0 Mon Sep 17 00:00:00 2001 From: alisdair sullivan Date: Thu, 29 Mar 2012 00:05:09 -0700 Subject: [PATCH] document dirty_strings in README --- README.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.markdown b/README.markdown index e9de71a..5b06ebe 100644 --- a/README.markdown +++ b/README.markdown @@ -127,6 +127,10 @@ javascript interpreters treat the codepoints `u+2028` and `u+2029` as significan json has no official comments but some parsers allow c style comments. this flag allows comments (both `// ...` and `/* ... */` style) anywhere whitespace is allowed +#### `dirty_strings` #### + +json escaping is lossy, it mutates the json string and repeated application can result in unwanted behaviour. if your strings are already escaped (or you'd like to force invalid strings into "json") use this flag to bypass escaping + ### incomplete input ###