umgeher/jsx
0
Fork 0
Code Issues Pull requests Activity

document dirty_strings in README

Browse source
This commit is contained in:
alisdair sullivan 2012-03-29 00:05:09 -07:00
parent 19e710da55
commit 73f4dadde5
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.markdown
View file

@ -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 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
### <a name="incompletes">incomplete input</a> ### ### <a name="incompletes">incomplete input</a> ###