Guy Oshiro

We discovered a bug in flexjson 3.2. It appears that it is forcibly perorming unicode encoding. String saved in DB: blah blah <> and <> \"href and othe Json output from flexjson 2.1-3.1 {"stringValue": "blah blah <> and <> \"href and other"} JSON output from flexjson 3.2 {"stringValue": "blah blah \u003c\u003e and \u003c\u003e \u0022href and other"} Is there an additional config / transformer that we need to set to avoid the unicode encoding in flexjson 3.2? i.e. < converted to \u003c We will roll...