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
I understand that you then get a more consistent set of data, but IMHO it sets a bad precedence, because the root object and kind property are no longer aligned (incorrect casing). If you have a custom resource with a few capital letters like, say HTTPRoute then this gets imported as
hTTPRoute: blah: {}
In short, we removed the strings.ToCamel when we import kubernetes resources and are quite happy with ConfigMap: foo: {} style data structures. In a way configMap looks like a typo, because that's not its kind
The text was updated successfully, but these errors were encountered:
Per @mogsie on Slack:
Why do all the examples of kubernetes resources on cuelang dot org use the ToCamel function when importing kind?
I understand that you then get a more consistent set of data, but IMHO it sets a bad precedence, because the root object and
kind
property are no longer aligned (incorrect casing). If you have a custom resource with a few capital letters like, sayHTTPRoute
then this gets imported asIn short, we removed the
strings.ToCamel
when we import kubernetes resources and are quite happy withConfigMap: foo: {}
style data structures. In a wayconfigMap
looks like a typo, because that's not its kindThe text was updated successfully, but these errors were encountered: