JSON parser improvement - to deal with utf exceptions
We use the Jade Rest service (& Json parser) as part of an interface to receive messages from our Customers, from a web page. The front end and all touch-points before the rest service are 3rd party software.
We get many Exceptions UE1416 (unicode to ansi conversion failed) or UE1418 (illegal byte sequence in utf8 chars). These exceptions cause a lot of 'noise' and inconvenience, so it would great to be able to handle these exceptions, either by a native handler, or by allowing us to add methods to the WebMessage (hidden) class.
Or allow a 'clean' of the incoming before parsing.
Software Medical Infomatics Limited 30/01/2018 1:08:52 PM
Hear hear. I've encountered these too and it would be great to handle them better.