`TransactionsApi` incorrect

[EnsuingRequiem]

The HybridTransaction model defines a non-optional var_date field, but the from_dict method validates API responses against a field date.

Field validation should be corrected to use var_date

[EnsuingRequiem]

Actually, looks like the error I'm experiencing is not related to the field var_date but the type of transaction not being returned from the get_transactions_by_month() API endpoint.

[bradymholt]

@EnsuingRequiem Can you give me some more detail? Are you passing in a type parameter to get_transactions_by_month?

[EnsuingRequiem]

@EnsuingRequiem Can you give me some more detail? Are you passing in a type parameter to get_transactions_by_month?

I'm not passing a type in since it is optional, but since get_transactions_by_month returns HybridTransactionResponse, when model validation is performed using the API response against the HybridTransaction model, the model validation fails due to type being just StrictStr instead of Optional[StrictStr].

If you perform the API request on the Transactions/getTransactions endpoint, the data returned actually aligns with the TransactionDetail model; HybridTransaction contains no field in the model for subtransactions, so even if the model were updated for type to be optional, I suspect there would be issues handling subtransactions.

To continue tinkering with the library, I updated the return typing for get_transactions_by_month, get_transactions_by_month_with_http_info, and get_transactions_by_month_without_preload_content to be TransactionsResponse instead of HybridTransactionsResponse for proper type hinting and then updated each of those method's _response_types_map to reflect the TransactionsResponse. Once I made those changes, I no longer received pydantic validation errors.

[bradymholt]

Thank you. The spec was incorrect and needed to be fixed. Fixed in #13 and released in v1.8.0