[Feature Request] Improve request and response type properties optionality

[mderriey]

Is your feature request related to a problem? Please describe.

Most request and response types have all their properties defined as optional, which makes it hard to work against, as we often have to resort to using the null-forgiving operator !..

Describe the solution you'd like

Types should be typed according to the OpenAPI spec and/or the OpenAPI spec should be improved to reflect the correct optionality.

For example, the OpenAPI definition for TransactionResponse defines id, status, and operation as required, yet the corresponding TypeScript type defines all these 3 properties as optional:

export interface TransactionResponse {
    /**
     * ID of the transaction.
     * @type {string}
     * @memberof TransactionResponse
     */
    'id'?: string;
    /**
     * The primary status of the transaction. For details, see [Primary transaction statuses](https://developers.fireblocks.com/reference/primary-transaction-statuses).
     * @type {string}
     * @memberof TransactionResponse
     */
    'status'?: string;
    /**
     * 
     * @type {GetTransactionOperation}
     * @memberof TransactionResponse
     */
    'operation'?: GetTransactionOperation;
}

Additional context

N/A.

[github-actions]

Your issue has been noted. We'll get back to you soon.

[mderriey]

@asafs932 is there a chance you could take a look at this? Having types that are closer to the OpenAPI model would help a lot from a consuming perspective.

[mderriey]

Any news?

[mderriey]

Hey there, any news on this?

[mghizzo]

+1

[Generalsimus]

+1