c5aa5c68bc
When dynamically-typed attributes are in the schema, we use different conventions for representing nested blocks containing them (using tuples and objects instead of lists and maps). The normalization code here doesn't deal with those because the legacy SDK never generates them, but we must still pass them through properly or else other SDKs will be blocked from using dynamic attributes. Previously this function would panic in that situation. Now it will just pass through nested blocks containing dynamic attribute values entirely as-is, with no normalization whatsoever. That's okay, because the scope of this function is only to normalize inconsistencies that the legacy SDK is known to produce, and the legacy SDK never produces dynamic-typed attributes. |
||
|---|---|---|
| .. | ||
| all_null.go | ||
| compatible.go | ||
| compatible_test.go | ||
| doc.go | ||
| lcs.go | ||
| lcs_test.go | ||
| normalize_obj.go | ||
| normalize_obj_test.go | ||
| objchange.go | ||
| objchange_test.go | ||
| plan_valid.go | ||
| plan_valid_test.go | ||