ynab 3.2.0 → 3.4.0

data/docs/SaveTransaction.md

@@ -1,19 +0,0 @@
-# YNAB::SaveTransaction
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **account_id** | **String** |  | [optional] |
-| **date** | **Date** | The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored. | [optional] |
-| **amount** | **Integer** | The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored. | [optional] |
-| **payee_id** | **String** | The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `tranfer_payee_id` on the account resource. | [optional] |
-| **payee_name** | **String** | The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee. | [optional] |
-| **category_id** | **String** | The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied. | [optional] |
-| **memo** | **String** |  | [optional] |
-| **cleared** | **String** | The cleared status of the transaction | [optional] |
-| **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
-| **flag_color** | **String** | The transaction flag | [optional] |
-| **import_id** | **String** | If specified, the new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in 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'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API). | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
-

data/docs/SaveTransactionWithId.md

@@ -1,20 +0,0 @@
-# YNAB::SaveTransactionWithId
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **id** | **String** |  | [optional] |
-| **account_id** | **String** |  | [optional] |
-| **date** | **Date** | The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored. | [optional] |
-| **amount** | **Integer** | The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored. | [optional] |
-| **payee_id** | **String** | The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `tranfer_payee_id` on the account resource. | [optional] |
-| **payee_name** | **String** | The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee. | [optional] |
-| **category_id** | **String** | The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied. | [optional] |
-| **memo** | **String** |  | [optional] |
-| **cleared** | **String** | The cleared status of the transaction | [optional] |
-| **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
-| **flag_color** | **String** | The transaction flag | [optional] |
-| **import_id** | **String** | If specified, the new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in 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'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API). | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
-

data/docs/SaveTransactionWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::SaveTransactionWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transaction** | [**SaveTransaction**](SaveTransaction.md) |  | 
-
-

data/docs/SaveTransactionsWrapper.md

@@ -1,9 +0,0 @@
-# YNAB::SaveTransactionsWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transaction** | [**SaveTransaction**](SaveTransaction.md) |  | [optional] 
-**transactions** | [**Array<SaveTransaction>**](SaveTransaction.md) |  | [optional] 
-
-

data/docs/ScheduledTransactionDetailAllOf.md

@@ -1,11 +0,0 @@
-# YNAB::ScheduledTransactionDetailAllOf
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **account_name** | **String** |  |  |
-| **payee_name** | **String** |  | [optional] |
-| **category_name** | **String** | The name of the category.  If a split scheduled transaction, this will be 'Split'. | [optional] |
-| **subtransactions** | [**Array<ScheduledSubTransaction>**](ScheduledSubTransaction.md) | If a split scheduled transaction, the subtransactions. |  |
-

data/docs/ScheduledTransactionWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::ScheduledTransactionWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**scheduled_transaction** | [**ScheduledTransactionDetail**](ScheduledTransactionDetail.md) |  | 
-
-

data/docs/ScheduledTransactionsWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::ScheduledTransactionsWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**scheduled_transactions** | [**Array<ScheduledTransactionDetail>**](ScheduledTransactionDetail.md) |  | 
-
-

data/docs/TransactionDetailAllOf.md

@@ -1,11 +0,0 @@
-# YNAB::TransactionDetailAllOf
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **account_name** | **String** |  |  |
-| **payee_name** | **String** |  | [optional] |
-| **category_name** | **String** | The name of the category.  If a split transaction, this will be 'Split'. | [optional] |
-| **subtransactions** | [**Array<SubTransaction>**](SubTransaction.md) | If a split transaction, the subtransactions. |  |
-

data/docs/TransactionWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::TransactionWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transaction** | [**TransactionDetail**](TransactionDetail.md) |  | 
-
-

data/docs/TransactionsWrapper.md

@@ -1,9 +0,0 @@
-# YNAB::TransactionsWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transactions** | [**Array<TransactionDetail>**](TransactionDetail.md) |  | 
-**server_knowledge** | **Integer** | The knowledge of the server | 
-
-

data/docs/UpdateTransaction.md

@@ -1,20 +0,0 @@
-# YNAB::UpdateTransaction
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**account_id** | **String** |  | 
-**date** | **Date** | The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored. | 
-**amount** | **Integer** | The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored. | 
-**payee_id** | **String** | The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `tranfer_payee_id` on the account resource. | [optional] 
-**payee_name** | **String** | The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee. | [optional] 
-**category_id** | **String** | The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied. | [optional] 
-**memo** | **String** |  | [optional] 
-**cleared** | **String** | The cleared status of the transaction | [optional] 
-**approved** | **BOOLEAN** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] 
-**flag_color** | **String** | The transaction flag | [optional] 
-**import_id** | **String** | If specified, the new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in 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'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API). | [optional] 
-**subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split.  Updating `subtransactions` on an existing split transaction is not supported. | [optional] 
-**id** | **String** |  | 
-
-

data/docs/UpdateTransactionsWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::UpdateTransactionsWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transactions** | [**Array<UpdateTransaction>**](UpdateTransaction.md) |  | 
-
-

data/docs/UserWrapper.md

@@ -1,8 +0,0 @@
-# YNAB::UserWrapper
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**user** | [**User**](User.md) |  | 
-
-

data/lib/ynab/models/budget_detail_all_of.rb

@@ -1,320 +0,0 @@
-=begin
-#YNAB API Endpoints
-
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
-
-The version of the OpenAPI document: 1.0.0
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.6.0
-
-=end
-
-require 'date'
-require 'time'
-
-module YNAB
-  class BudgetDetailAllOf
-    attr_accessor :accounts
-
-    attr_accessor :payees
-
-    attr_accessor :payee_locations
-
-    attr_accessor :category_groups
-
-    attr_accessor :categories
-
-    attr_accessor :months
-
-    attr_accessor :transactions
-
-    attr_accessor :subtransactions
-
-    attr_accessor :scheduled_transactions
-
-    attr_accessor :scheduled_subtransactions
-
-    # Attribute mapping from ruby-style variable name to JSON key.
-    def self.attribute_map
-      {
-        :'accounts' => :'accounts',
-        :'payees' => :'payees',
-        :'payee_locations' => :'payee_locations',
-        :'category_groups' => :'category_groups',
-        :'categories' => :'categories',
-        :'months' => :'months',
-        :'transactions' => :'transactions',
-        :'subtransactions' => :'subtransactions',
-        :'scheduled_transactions' => :'scheduled_transactions',
-        :'scheduled_subtransactions' => :'scheduled_subtransactions'
-      }
-    end
-
-    # Returns all the JSON keys this model knows about
-    def self.acceptable_attributes
-      attribute_map.values
-    end
-
-    # Attribute type mapping.
-    def self.openapi_types
-      {
-        :'accounts' => :'Array<Account>',
-        :'payees' => :'Array<Payee>',
-        :'payee_locations' => :'Array<PayeeLocation>',
-        :'category_groups' => :'Array<CategoryGroup>',
-        :'categories' => :'Array<Category>',
-        :'months' => :'Array<MonthDetail>',
-        :'transactions' => :'Array<TransactionSummary>',
-        :'subtransactions' => :'Array<SubTransaction>',
-        :'scheduled_transactions' => :'Array<ScheduledTransactionSummary>',
-        :'scheduled_subtransactions' => :'Array<ScheduledSubTransaction>'
-      }
-    end
-
-    # List of attributes with nullable: true
-    def self.openapi_nullable
-      Set.new([
-      ])
-    end
-
-    # Initializes the object
-    # @param [Hash] attributes Model attributes in the form of hash
-    def initialize(attributes = {})
-      if (!attributes.is_a?(Hash))
-        fail ArgumentError, "The input argument (attributes) must be a hash in `YNAB::BudgetDetailAllOf` initialize method"
-      end
-
-      # check to see if the attribute exists and convert string to symbol for hash key
-      attributes = attributes.each_with_object({}) { |(k, v), h|
-        if (!self.class.attribute_map.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `YNAB::BudgetDetailAllOf`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
-        end
-        h[k.to_sym] = v
-      }
-
-      if attributes.key?(:'accounts')
-        if (value = attributes[:'accounts']).is_a?(Array)
-          self.accounts = value
-        end
-      end
-
-      if attributes.key?(:'payees')
-        if (value = attributes[:'payees']).is_a?(Array)
-          self.payees = value
-        end
-      end
-
-      if attributes.key?(:'payee_locations')
-        if (value = attributes[:'payee_locations']).is_a?(Array)
-          self.payee_locations = value
-        end
-      end
-
-      if attributes.key?(:'category_groups')
-        if (value = attributes[:'category_groups']).is_a?(Array)
-          self.category_groups = value
-        end
-      end
-
-      if attributes.key?(:'categories')
-        if (value = attributes[:'categories']).is_a?(Array)
-          self.categories = value
-        end
-      end
-
-      if attributes.key?(:'months')
-        if (value = attributes[:'months']).is_a?(Array)
-          self.months = value
-        end
-      end
-
-      if attributes.key?(:'transactions')
-        if (value = attributes[:'transactions']).is_a?(Array)
-          self.transactions = value
-        end
-      end
-
-      if attributes.key?(:'subtransactions')
-        if (value = attributes[:'subtransactions']).is_a?(Array)
-          self.subtransactions = value
-        end
-      end
-
-      if attributes.key?(:'scheduled_transactions')
-        if (value = attributes[:'scheduled_transactions']).is_a?(Array)
-          self.scheduled_transactions = value
-        end
-      end
-
-      if attributes.key?(:'scheduled_subtransactions')
-        if (value = attributes[:'scheduled_subtransactions']).is_a?(Array)
-          self.scheduled_subtransactions = value
-        end
-      end
-    end
-
-    # Show invalid properties with the reasons. Usually used together with valid?
-    # @return Array for valid properties with the reasons
-    def list_invalid_properties
-      invalid_properties = Array.new
-      invalid_properties
-    end
-
-    # Check to see if the all the properties in the model are valid
-    # @return true if the model is valid
-    def valid?
-      true
-    end
-
-    # Checks equality by comparing each attribute.
-    # @param [Object] Object to be compared
-    def ==(o)
-      return true if self.equal?(o)
-      self.class == o.class &&
-          accounts == o.accounts &&
-          payees == o.payees &&
-          payee_locations == o.payee_locations &&
-          category_groups == o.category_groups &&
-          categories == o.categories &&
-          months == o.months &&
-          transactions == o.transactions &&
-          subtransactions == o.subtransactions &&
-          scheduled_transactions == o.scheduled_transactions &&
-          scheduled_subtransactions == o.scheduled_subtransactions
-    end
-
-    # @see the `==` method
-    # @param [Object] Object to be compared
-    def eql?(o)
-      self == o
-    end
-
-    # Calculates hash code according to all attributes.
-    # @return [Integer] Hash code
-    def hash
-      [accounts, payees, payee_locations, category_groups, categories, months, transactions, subtransactions, scheduled_transactions, scheduled_subtransactions].hash
-    end
-
-    # Builds the object from hash
-    # @param [Hash] attributes Model attributes in the form of hash
-    # @return [Object] Returns the model itself
-    def self.build_from_hash(attributes)
-      new.build_from_hash(attributes)
-    end
-
-    # Builds the object from hash
-    # @param [Hash] attributes Model attributes in the form of hash
-    # @return [Object] Returns the model itself
-    def build_from_hash(attributes)
-      return nil unless attributes.is_a?(Hash)
-      attributes = attributes.transform_keys(&:to_sym)
-      self.class.openapi_types.each_pair do |key, type|
-        if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key)
-          self.send("#{key}=", nil)
-        elsif type =~ /\AArray<(.*)>/i
-          # check to ensure the input is an array given that the attribute
-          # is documented as an array but the input is not
-          if attributes[self.class.attribute_map[key]].is_a?(Array)
-            self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
-          end
-        elsif !attributes[self.class.attribute_map[key]].nil?
-          self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
-        end
-      end
-
-      self
-    end
-
-    # Deserializes the data based on type
-    # @param string type Data type
-    # @param string value Value to be deserialized
-    # @return [Object] Deserialized data
-    def _deserialize(type, value)
-      case type.to_sym
-      when :Time
-        Time.parse(value)
-      when :Date
-        Date.parse(value)
-      when :String
-        value.to_s
-      when :Integer
-        value.to_i
-      when :Float
-        value.to_f
-      when :Boolean
-        if value.to_s =~ /\A(true|t|yes|y|1)\z/i
-          true
-        else
-          false
-        end
-      when :Object
-        # generic object (usually a Hash), return directly
-        value
-      when /\AArray<(?<inner_type>.+)>\z/
-        inner_type = Regexp.last_match[:inner_type]
-        value.map { |v| _deserialize(inner_type, v) }
-      when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
-        k_type = Regexp.last_match[:k_type]
-        v_type = Regexp.last_match[:v_type]
-        {}.tap do |hash|
-          value.each do |k, v|
-            hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
-          end
-        end
-      else # model
-        # models (e.g. Pet) or oneOf
-        klass = YNAB.const_get(type)
-        klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
-      end
-    end
-
-    # Returns the string representation of the object
-    # @return [String] String presentation of the object
-    def to_s
-      to_hash.to_s
-    end
-
-    # to_body is an alias to to_hash (backward compatibility)
-    # @return [Hash] Returns the object in the form of hash
-    def to_body
-      to_hash
-    end
-
-    # Returns the object in the form of hash
-    # @return [Hash] Returns the object in the form of hash
-    def to_hash
-      hash = {}
-      self.class.attribute_map.each_pair do |attr, param|
-        value = self.send(attr)
-        if value.nil?
-          is_nullable = self.class.openapi_nullable.include?(attr)
-          next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
-        end
-
-        hash[param] = _to_hash(value)
-      end
-      hash
-    end
-
-    # Outputs non-array value in the form of hash
-    # For object, use to_hash. Otherwise, just return the value
-    # @param [Object] value Any valid value
-    # @return [Hash] Returns the value in the form of hash
-    def _to_hash(value)
-      if value.is_a?(Array)
-        value.compact.map { |v| _to_hash(v) }
-      elsif value.is_a?(Hash)
-        {}.tap do |hash|
-          value.each { |k, v| hash[k] = _to_hash(v) }
-        end
-      elsif value.respond_to? :to_hash
-        value.to_hash
-      else
-        value
-      end
-    end
-
-  end
-
-end