cty/json: Allow unsupported fields in json about go-cty HOT 2 CLOSED

Hi @akupila! Sorry for the slow response here.

The json package here was intended to prioritize being explicit, so the strictness you refer to is conceived as a feature rather than a bug. However, as you've noted it can be useful to take a more flexible approach when dealing with interchange between different systems or different versions of the same system, which includes not only allowing for undeclared attributes but possibly other allowances, such as an attribute that was previously defined as a number but is now a string.

The explicit conversion approach you found in your second playground example here is nice, I think, because it accommodates various sorts of structural differences as long as there's a type conversion available for them. For that reason, I'm going to close this with the recommendation of using the conversion approach you found in situations where a less-strict approach is warranted.

Thanks for raising this, and thanks for sharing the compromise approach you found!

from go-cty.

Perhaps this is not necessary, this seems like a reasonable workaround: https://play.golang.org/p/rvjnUJZOvRU

from go-cty.