Plural:   "plural2",
						Singular: "singular2",
						Kind:     "kind2",
						ListKind: "listkind2",
					},
					PreserveUnknownFields: pointer.BoolPtr(true),
				},
				Status: apiextensions.CustomResourceDefinitionStatus{
					AcceptedNames: apiextensions.CustomResourceDefinitionNames{
						Plural:   "plural2",
						Singular: "singular2",
						Kind:     "kind2",

## Valores singulares no corpo

Assim como existem uma `Query` e uma `Path` para definir dados adicionais para parâmetros de consulta e de rota, o **FastAPI** provê o equivalente para `Body`.

Por exemplo, extendendo o modelo anterior, você poder decidir por ter uma outra chave `importance` no mesmo corpo, além de `item` e `user`.

// with apply.
type CustomResourceDefinitionNamesApplyConfiguration struct {
	Plural     *string  `json:"plural,omitempty"`
	Singular   *string  `json:"singular,omitempty"`
	ShortNames []string `json:"shortNames,omitempty"`
	Kind       *string  `json:"kind,omitempty"`
	ListKind   *string  `json:"listKind,omitempty"`
	Categories []string `json:"categories,omitempty"`
}

// with apply.
type CustomResourceDefinitionNamesApplyConfiguration struct {
	Plural     *string  `json:"plural,omitempty"`
	Singular   *string  `json:"singular,omitempty"`
	ShortNames []string `json:"shortNames,omitempty"`
	Kind       *string  `json:"kind,omitempty"`
	ListKind   *string  `json:"listKind,omitempty"`
	Categories []string `json:"categories,omitempty"`
}

            + optionalNumber(", ", skipped, " skipped"));
    }

    private String mandatoryNumber(long value, String singular, String plural) {
        return value == 1 ? value + singular : value + plural;
    }

    private String optionalNumber(String separator, long value, String description) {
        return value == 0 ? "" : separator + value + description;
    }

	Scope ResourceScope
	// singularResource is the singular name of the resource.  This allows clients to handle plural and singular opaquely.
	// For many clients the singular form of the resource will be more understandable to users reading messages and should be used when integrating the name of the resource into a sentence.
	// The command line tool kubectl, for example, allows use of the singular resource name in place of plurals.

        "fieldsV1": {},
        "subresource": "subresourceValue"
      }
    ]
  },
  "spec": {
    "group": "groupValue",
    "names": {
      "plural": "pluralValue",
      "singular": "singularValue",
      "shortNames": [
        "shortNamesValue"
      ],
      "kind": "kindValue",
      "listKind": "listKindValue",
      "categories": [
        "categoriesValue"
      ]
    },

  optional string scope = 3;

  // singularResource is the singular name of the resource.  This allows clients to handle plural and singular opaquely.
  // For many clients the singular form of the resource will be more understandable to users reading messages and should be used when integrating the name of the resource into a sentence.
  // The command line tool kubectl, for example, allows use of the singular resource name in place of plurals.

  group: groupValue
  names:
    categories:
    - categoriesValue
    kind: kindValue
    listKind: listKindValue
    plural: pluralValue
    shortNames:
    - shortNamesValue
    singular: singularValue
  preserveUnknownFields: true
  scope: scopeValue
  versions:
  - additionalPrinterColumns:
    - description: descriptionValue
      format: formatValue
      jsonPath: jsonPathValue

  optional string scope = 3;

  // singularResource is the singular name of the resource.  This allows clients to handle plural and singular opaquely.
  // For many clients the singular form of the resource will be more understandable to users reading messages and should be used when integrating the name of the resource into a sentence.
  // The command line tool kubectl, for example, allows use of the singular resource name in place of plurals.