ef086399f9
The Legacy SDK cannot handle missing strings from objects in sets, and will insert an empty string when planning the missing value. This subverts the `couldHaveUnknownBlockPlaceholder` check, and causes errors when `dynamic` is used with NestingSet blocks. We don't have a separate codepath to handle the internals of AssertObjectCompatible differently for the legacy SDK, but we can treat empty strings as null strings within set objects to avoid the failed assertions. |
||
|---|---|---|
| .. | ||
| action.go | ||
| 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 | ||