Issue with capitalization in printcolumn names about crossplane HOT 4 CLOSED

I tend to agree with @phisco - k9s should be able to handle the data in whatever format it is given. Are we going to change all of the providers too? This seems like a lot of unnecessary effort to work around something that k9s could fix in one place.

from crossplane.

Feels also that K9s could be more flexible and match both uppercase and Camel case columns 🤔 not a big issue changing it here, but I guess we won't be the only one, at a quick look I could see a few projects doing the same, e.g. https://github.com/kyverno/kyverno/blob/main/config/crds/kyverno/kyverno.io_admissionreports.yaml, but also upstream components.

from crossplane.

Yeah, it doesn't seem like there's any clear guidance.

I notice the CRD docs use title case column name examples (e.g. Age). There doesn't seem to be any enforcement of this though, and the API reference docs just say "a human readable name for the column" without any details about format.

AFAIK kubectl is always going to show these as title case no matter what format we use.

So all that said unless there's clear guidance that we should be following a convention I agree it would be best to update k9s to address this, not Crossplane.

from crossplane.

Yes, valid point. Thanks for your feedback! 🚀

from crossplane.