Don't fail deserialization with carpentry errors IFF the carpented types would be discarded through evolution

Description

NOTE: This is the V3 version of this issue

It's possible to fail to carpent up types and fail deserialization accordingly when the failure shouldn't actually matter. That is, the type the receiving node doesn't know about (and cannot synthesise) is part of the evolution of the type and won't be a part of the evolved deserialised form.

In such a case, it makes no sense to propagate the carpentry error to the rest of the system

Raising This as 2 Jira's, one targeting V3 as high priority and one targetting V4 / Master as medium priority

Partly because of the split in priorty, partly because the codebase divergence makes it essentially two bodies of work

Activity

Show:
Katelyn Baker
March 18, 2019, 1:12 PM

Assignee

Katelyn Baker

Reporter

Katelyn Baker

Labels

Sprint

None

Epic Link

None

Priority

High

Engineering Teams

None

Fix versions

Affects versions

Story Points / Dev Days

None

Build cut

None

Moscow Priority

None
Configure