Field requirements in OpenAPI spec - all fields optional due to missing 'required' array"?

[mt-bt]

Hello,

I noticed that throughout the Etsy OpenAPI specification, schemas define fields with nullable: true/false but don't specify the required array at the object level (or the required property for each field). According to the OpenAPI specification, this means all fields are technically optional, regardless of their nullable status.

For example, in the User schema:

"User": {
    "type": "object",
    "properties": {
        "user_id": {
            "type": "integer",
            "minimum": 1
        },
        "primary_email": {
            "type": "string",
            "format": "email",
            "nullable": true
        }
        // ... other fields
    }
}

This seems counterintuitive - user_id would logically be a required field for a User object, but without being listed in a required array at the schema level, it's technically optional according to the spec.

Questions:

• Is this intentional? Should we assume all fields are truly optional?
• Or was the intention that only fields marked with nullable: true should be optional, and the required array is missing from the spec?

Context: I'm using swagger-typescript-api to generate a TypeScript SDK, and having all fields marked as optional (?:) in the generated types/SDK feels incorrect, especially for fundamental fields like user_id.

Thanks

[mggevaer]

Running into the same thing on objects such as "ShopListingWithAssociations" which has all fields as optional, while one would expect listingId to be required.
Would be willing to do a PR that fixes some of the more obvious cases, but the json has been removed from the repo.

This is leading to a lot more code, and having to guess which missing data really needs to be accounted for with error handling, warning pages etc... and which data is just always going to be there anyway.