On 30.04.24 19:39, Jacob Champion wrote:
Tangentially: Should we maybe rethink pieces of the json_lex_string error handling? For example, do we really want to echo an incomplete multibyte sequence once we know it's bad?
I can't quite find the place you might be looking at in json_lex_string(), but for the general encoding conversion we have what would appear to be the same behavior in report_invalid_encoding(), and we go out of our way there to produce a verbose error message including the invalid data.
