Invalid json (with latin1 chars) get parsed instead of throwing an exception

[dominikzogg]

I've tried to enhance error handling of my deserializer library (https://github.com/chubbyphp/chubbyphp-deserialization/blob/master/src/Decoder/JsonTypeDecoder.php) and wished to support native json_decode and your library (what the library user prefers).

While testing i've seen, that the parser seems to allow latin1 chars within the json.
What i know, json needs to be utf-8 (or asci).

[dominikzogg]

chubbyphp-legacy/chubbyphp-deserialization#18

[Seldaek]

Interesting.. Not sure how we could fix this though, if you have a suggestion feel free.

[staabm]

so the question is: should the linter check the whole file for non-utf8 characters, right?

[Seldaek]

I guess it should reject any invalid utf8 char yes.

[dominikzogg]

@Seldaek a check having at least two chars > 127 instead of one would probably fix most, but it would be still possible having 'ää' as latin1 which seems to be utf-8 then