add support of JSON_UNESCAPED_UNICODE

[rznzippy]

add unescapedUnicode option to Zend\Json::encode #6848 #7206

[Ocramius]

While I understand why this was implemented, I don't see an actual use-case.

What is it for, exactly? Seems like an un-needed security risk to me...

[rznzippy]

Hello Marco,

First of all I'ld like to say thank you for your time.

We're using this option for two reasons:

• we have integration with android application that unable to recognise encoded unicode characters
• with this option we could put human-readable request/response text to text log files

For now we have to have our own implementation of Json and JsonModel classes, because there is no easy way to pass JSON_UNESCAPED_UNICODE option into json_encode function inside Json class.

So main pros that I can see:

• be able to integrate with some applications that doesn't support encoded unicode characters
• human-readable output in console and log files
• reduced size of json string

[weierophinney]

I agree with @Ocramius that this is a security risk. As such, you're already following the appropriate course of action, @rznzippy : extending and overriding the renderer and model present in the framework. (This is why we have an IoC container and configurable renderers!)