I must not be following the UX for this tool
1. click configmap in the sidebar
1. observe configmap dialog in the layout
Also observe that the "kind" is "Configmap" but the Kubernetes resource is ConfigMap, as one can see here https://kubernetes.io/docs/reference/generated/kubernetes-ap...
Your tool does the same thing for CronJob being erroneously written as Cronjob so it is a systemic problem
1. expand "data" chevron
1. be sad because nothing else is possible
1. ok, so type "true" into the "immutable" field. It doesn't seem to turn the red icon green. Type "my dog is snoopy". Nothing else changes
Be aware that, yes, there are "status" responses on a bunch of the objects, but to the very best of my knowledge one can never set a "status" because the user doesn't control the status rather reality controls the status, otherwise I'd cheerfully always set my Pods to never CLBO :-P
Thank you for that insight, indeed k8s uses pascal case. I have opened an issue to investigate further and resolve. https://github.com/kubenote/KubeForge/issues/10
The color of the fields is not based on right or wrong but based on typing. Green is string, red is boolean, orange is object, purple is array, etc. I can definitely make that more apparent. https://github.com/kubenote/KubeForge/issues/11
As for the empty object, there are a lot of objects are that incomplete that I need to go through and apply manual override definitions for (https://github.com/kubenote/KubeForge/blob/main/src/componen...). Thank you for pointing out the two above. https://github.com/kubenote/KubeForge/issues/12
For the fields that exist but aren't feasible for users to interact with, currently I'm puling in the schemas raw. but I do want to create a preferred fields override with commonly edited and changed fields to reduce clutter. https://github.com/kubenote/KubeForge/issues/13
Thank you for the awesome feedback!