"schema": {"$ref": "#/components/schemas/Item"}
                                }
                            },
                            "required": True,
                        },
                        "responses": {
                            "200": {
                                "description": "Successful Response",

 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,

 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the

The way to describe this in OpenAPI, is to mark that field as **required**, because it will always be there.

Because of that, the JSON Schema for a model can be different depending on if it's used for **input or output**:

* for **input** the `description` will **not be required**
* for **output** it will be **required** (and possibly `None`, or in JSON terms, `null`)

        - binary
    validations:
      required: true

  - type: input
    id: tfversion
    attributes:
      label: TensorFlow version
      placeholder: e.g., tf 2.8
    validations:
      required: true
  - type: dropdown
    id: Code
    attributes:
      label: Custom code
      options:
        - "Yes"
        - "No"
    validations:
      required: true
  - type: input
    id: OS

    public Integer crudMode;

    /** Configuration name for identifying this data source */
    @Required
    @Size(max = 200)
    public String name;

    /** Optional description of this data configuration */
    @Size(max = 1000)
    public String description;

    /** Handler class name for processing this data source */
    @Required
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String handlerName;

@pytest.mark.parametrize(
    "path,expected_status,expected_response",
    [
        ("/default", 200, {"foo": "foo"}),
        ("/default?foo=bar", 200, {"foo": "bar"}),
        ("/required?foo=bar", 200, {"foo": "bar"}),
        ("/required", 422, foo_is_missing),
        ("/required?foo=", 422, foo_is_short),
        ("/multiple?foo=bar", 200, {"foo": "bar"}),
        ("/multiple", 422, foo_is_missing),
        ("/multiple?foo=", 422, foo_is_short),

    /** The boost value for search ranking (required). */
    @Required
    @ValidateTypeFailure
    public Float boost;

    /** Whether this configuration is available for crawling (required, maximum 5 characters). */
    @Required
    @Size(max = 5)
    public String available;

    /** The permissions required to access documents from this configuration. */

    validations:
      required: true

  - type: textarea
    attributes:
      label: 2. What's the best code you can write to accomplish that without the new feature?
    validations:
      required: true

  - type: textarea
    attributes:
      label: 3. What would that same code look like if we added your feature?
    validations:
      required: true

  - type: markdown
    attributes:

                        "title": "Item",
                        "required": ["data"],
                        "type": "object",
                        "properties": {"data": {"title": "Data", "type": "string"}},
                    },
                    "ValidationError": {
                        "title": "ValidationError",
                        "required": ["loc", "msg", "type"],
                        "type": "object",