使用 OpenAPI 规范保持单一资源表示方法

阅读此post(参见:3 How to use a single definition when...)关于使用 OpenAPI 描述 REST API(Swagger) 规范，您可以注意如何使用 readOnly 属性保留单个资源表示来添加/更新和获取资源，而不是使用一种表示来获取(获取集合项)和另一种表示用于添加(POST 到一个集合).例如，在下面的 User 单一表示中，id 是一个只读属性，这意味着它不会在创建用户时在表示中发送，它会在用户创建时发送已检索.

Reading this post (see: 3 How to use a single definition when...) about describing a REST API using OpenAPI (Swagger) specification you can note how to keep a single resource representation for adding/updating and getting resource using readOnly property instead of having one representation for getting (GET a collection item) and other one for adding (POST to a collection). For example, in the following User single representation, the id is a read-only property which mean that it won't be sent in the representation when a user is created, it will be there when a user is retrieved.

"User":
{
    "type": "object",
    "properties": {
        "id": {
            "type": "integer",
            "format": "int64",
            "readOnly": true
        },
        "company_data": {
            "type": "object",
            "properties": {
                .
                .
                .
            },
            "readOnly": false
        }
    }
}

保持资源表示列表尽可能短真的很干净而且很好，所以我想保持单一资源表示方法，但我面临的问题是:如何管理必需 当一个属性是强制输入时?假设我需要在创建用户时根据需要设置 company_data (POST/users/)，但在检索用户时不需要设置 (GET/users/{user_id}).OpenAPI 规范中有什么方法可以在不丢失单一资源表示的情况下满足这种需求?

It is really clean and nice to keep the list of resource representation as short as possible so I want to keep the single resource representation approach but the problem I am facing to do that is: how to manage required when a property is mandatory for input only? Suppose I need to set company_data as required when the user is created (POST /users/) but non-required when an user is retrieved (GET /users/{user_id}). There are any way in OpenAPI specification to satisfy this need without lost the single resource representation?