Show wrong ConfigMap data

[chivalryq]

Describe the bug
Use command to show a ConfigMap, the content is different with the actual value (velua from with command or kubectl get)

Wrong content

content, notice the "ClassInSpec"[] near to end:

Now if you the content, you'll get the same wrong configmap content in clipboard.

Actual content

True configmap content, shown by command:

It's same with kuebctl get

kubectl get cm -n vela-system trait-schema-gateway-v6 -oyaml
apiVersion: v1
data:
  openapi-v3-json-schema: '{"properties":{"class":{"default":"nginx","description":"Specify
    the class of ingress to use","title":"class","type":"string"},"classInSpec":{"default":false,"description":"Set
    ingress class in ''.spec.ingressClassName'' instead of ''kubernetes.io/ingress.class''
    annotation.","title":"classInSpec","type":"boolean"},"domain":{"description":"Specify
    the domain you want to expose","title":"domain","type":"string"},"gatewayHost":{"description":"Specify
    the host of the ingress gateway, which is used to generate the endpoints when
    the host is empty.","title":"gatewayHost","type":"string"},"http":{"additionalProperties":{"type":"integer"},"description":"Specify
    the mapping relationship between the http path and the workload port","title":"http","type":"object"},"secretName":{"description":"Specify
    the secret name you want to quote to use tls.","title":"secretName","type":"string"}},"required":["http","class","classInSpec"],"type":"object"}'
kind: ConfigMap
metadata:
  annotations:
    definition.oam.dev/appliedWorkloads: deployments.apps,statefulsets.apps
  creationTimestamp: "2023-07-21T06:33:15Z"
  labels:
    definition.oam.dev: schema
    definition.oam.dev/name: gateway-v6
  name: trait-schema-gateway-v6
  namespace: vela-system
  ownerReferences:
  - apiVersion: core.oam.dev/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: DefinitionRevision
    name: gateway-v6
    uid: 4ecdf779-a181-43b3-8d0c-9cbd9bb91899
  resourceVersion: "25244925"
  uid: 7d79e8ec-1cdf-4df8-8c1d-c96dd33d726e

To Reproduce
Steps to reproduce the behavior:

1. Use this configmap:

apiVersion: v1
data:
  openapi-v3-json-schema: '{"properties":{"class":{"default":"nginx","description":"Specify
    the class of ingress to use","title":"class","type":"string"},"classInSpec":{"default":false,"description":"Set
    ingress class in ''.spec.ingressClassName'' instead of ''kubernetes.io/ingress.class''
    annotation.","title":"classInSpec","type":"boolean"},"domain":{"description":"Specify
    the domain you want to expose","title":"domain","type":"string"},"gatewayHost":{"description":"Specify
    the host of the ingress gateway, which is used to generate the endpoints when
    the host is empty.","title":"gatewayHost","type":"string"},"http":{"additionalProperties":{"type":"integer"},"description":"Specify
    the mapping relationship between the http path and the workload port","title":"http","type":"object"},"secretName":{"description":"Specify
    the secret name you want to quote to use tls.","title":"secretName","type":"string"}},"required":["http","class","classInSpec"],"type":"object"}'
kind: ConfigMap
metadata:
  name: a-schema-configmap
  namespace: default

2. Follow the step mentioned above.

Expected behavior
A clear and concise description of what you expected to happen.
The view show the right ConfigMap content.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: OSX
• K9s: 0.27.4
• K8s: 1.26.3

Additional context
Add any other context about the problem here.