You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Great library and very useful for me and my team. Thank you for taking the time to write and maintain it.
When updating from 0.118.0 to 0.124.0 some of our consuming code broke and I am looking for the correct remediation. For example we had some code that looked like the following:
I don't know if getting the Type at index 0 is correct, but looking at the MarshalYaml() makes me think that's the right thing to do. I see JSON schemas supports multiple types. I did not realize this. The schemas we are parsing, for now, only use a single type.
The text was updated successfully, but these errors were encountered:
I think that's correct because Type.Is uses the type at index 0 as well. At least that's what I've been using in my PR at metio/terraform-provider-k8s#120 to update to the latest version.
Hello! Great library and very useful for me and my team. Thank you for taking the time to write and maintain it.
When updating from
0.118.0
to0.124.0
some of our consuming code broke and I am looking for the correct remediation. For example we had some code that looked like the following:This is no longer valid with the new structure of the Schema object. When investigating, I found I could do something like this:
I don't know if getting the
Type
at index0
is correct, but looking at the MarshalYaml() makes me think that's the right thing to do. I see JSON schemas supports multiple types. I did not realize this. The schemas we are parsing, for now, only use a single type.The text was updated successfully, but these errors were encountered: