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
{{ message }}
Repository navigation
Create a hook for intercepting serialisiation errors #1333
We don't just want to provide a default value in case certain fields can't be parsed or are not present in the JSON. But also intercept these issues so we can log & monitor it, when it happens.
Example DSLs
1)
abstract class MyValue {
@BuiltValueHook(<deserializationError>: true)
static void _logError(MyValueBuilder b, Exception e, String key) => logger.logError(ParsingError(e, key))
or maybe even better would be to do the same globally
2) A global plugin that logs all deserialization exceptions 🤔
This is assuming if @nullable is used and if that field can't be parsed, the value will be null and now exceptions will be thrown
I think catching DeserializationError is something you can already do? Either by wrapping your RPC handling code in try/catch or by installing a Zone error handler to catch them.
Activity
davidmorgan commentedon Dec 11, 2024
This looks related to #1293.
I think catching
DeserializationErroris something you can already do? Either by wrapping your RPC handling code intry/catchor by installing aZoneerror handler to catch them.