You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without mentioned flag, json looks like followed and decoding is fine:
["P\u0159edm\u011bty"]
Honestly, I don't know much about JSON standard, so I don't know how problematic BC break it is. And maybe it is an issue of PowerShell at all, I didn't find any relevant info.
As a workaround I use CallbackResponse and own JSON encoding.
The text was updated successfully, but these errors were encountered:
Version: dev (73742cf)
Bug Description
JsonRespose uses Json::encode(). It has default flag
JSON_UNESCAPED_UNICODE
set.For example, encoding result of
["Předměty"]
is:["Předměty"]
When I decode such data in PowerShell (v5.1 on Windows Server 2012):
I get malformed output like
P??edm??ty
.Without mentioned flag, json looks like followed and decoding is fine:
["P\u0159edm\u011bty"]
Honestly, I don't know much about JSON standard, so I don't know how problematic BC break it is. And maybe it is an issue of PowerShell at all, I didn't find any relevant info.
As a workaround I use
CallbackResponse
and own JSON encoding.The text was updated successfully, but these errors were encountered: