update openapi spec and regenerate with newer openapi-generator

the newer openapi-generator picks up fixes for optional parameters,
among other things

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/TransactionSummary.md b/docs/TransactionSummary.md
index fd93b15..e8e7db6 100644
--- a/docs/TransactionSummary.md
+++ b/docs/TransactionSummary.md
@@ -5,19 +5,19 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **id** | **String** |  | 
-**date** | [***String**](string.md) | The transaction date in ISO format (e.g. 2016-12-01) | 
+**date** | [**String**](string.md) | The transaction date in ISO format (e.g. 2016-12-01) | 
 **amount** | **i64** | The transaction amount in milliunits format | 
-**memo** | **String** |  | [optional] 
+**memo** | Option<**String**> |  | [optional]
 **cleared** | **String** | The cleared status of the transaction | 
 **approved** | **bool** | Whether or not the transaction is approved | 
-**flag_color** | **String** | The transaction flag | [optional] 
+**flag_color** | Option<**String**> | The transaction flag | [optional]
 **account_id** | **String** |  | 
-**payee_id** | **String** |  | [optional] 
-**category_id** | **String** |  | [optional] 
-**transfer_account_id** | **String** | If a transfer transaction, the account to which it transfers | [optional] 
-**transfer_transaction_id** | **String** | If a transfer transaction, the id of transaction on the other side of the transfer | [optional] 
-**matched_transaction_id** | **String** | If transaction is matched, the id of the matched transaction | [optional] 
-**import_id** | **String** | If the Transaction was imported, this field is a unique (by account) import identifier.  If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'.  For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. | [optional] 
+**payee_id** | Option<**String**> |  | [optional]
+**category_id** | Option<**String**> |  | [optional]
+**transfer_account_id** | Option<**String**> | If a transfer transaction, the account to which it transfers | [optional]
+**transfer_transaction_id** | Option<**String**> | If a transfer transaction, the id of transaction on the other side of the transfer | [optional]
+**matched_transaction_id** | Option<**String**> | If transaction is matched, the id of the matched transaction | [optional]
+**import_id** | Option<**String**> | If the Transaction was imported, this field is a unique (by account) import identifier.  If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'.  For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. | [optional]
 **deleted** | **bool** | Whether or not the transaction has been deleted.  Deleted transactions will only be included in delta requests. | 
 
 [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)