As discussed in #136, this was a breaking change. Implementing UnmarshalJSON on JSONWebKeySet broke unmarshaling into structs that embed JSONWebKeySet and also include other fields (and that do not have UnmarshalJSON implementations themselves). Before #130, those fields would get unmarshaled using the default behavior for encoding/json. After #130, the custom UnmarshalJSON would get called for the whole parent struct, but because its receiver is the embedded JSONWebKeySet it would not be able to set any of the sibling fields.
Revert for now to undo the breakage. We should find another way to solve the problem of accepting unrecognized keys.
As discussed in #136, this was a breaking change. Implementing
UnmarshalJSONonJSONWebKeySetbroke unmarshaling into structs that embedJSONWebKeySetand also include other fields (and that do not haveUnmarshalJSONimplementations themselves). Before #130, those fields would get unmarshaled using the default behavior forencoding/json. After #130, the customUnmarshalJSONwould get called for the whole parent struct, but because its receiver is the embeddedJSONWebKeySetit would not be able to set any of the sibling fields.Revert for now to undo the breakage. We should find another way to solve the problem of accepting unrecognized keys.