self
keep trying to deserialize an object after an error?This behavior takes effect after each attribute deserialization with
errors such as a missing attribute or the value is of the wrong type.
If keep_going
, the attribute will be skipped but the engine will
deserialize the next attribute.
If not keep_going
, the engine stops deserializing right away.
When at true
, this may cause the accumulation of a lot of entries in errors
.
Default at true
.
# Should `self` keep trying to deserialize an object after an error?
#
# This behavior takes effect after each attribute deserialization with
# errors such as a missing attribute or the value is of the wrong type.
# If `keep_going`, the attribute will be skipped but the engine will
# deserialize the next attribute.
# If `not keep_going`, the engine stops deserializing right away.
#
# When at `true`, this may cause the accumulation of a lot of entries in `errors`.
#
# Default at `true`.
var keep_going: nullable Bool = null is writable
lib/serialization/serialization_core.nit:159,2--170,49