hubspot-api-client 17.2.0 → 18.0.0

data/lib/hubspot/codegen/cms/hubdb/models/error.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,37 +17,37 @@ module Hubspot
   module Cms
     module Hubdb
       class Error
-        # A human readable message describing the error along with remediation steps where appropriate
-        attr_accessor :message
+        # A specific category that contains more specific detail about the error
+        attr_accessor :sub_category
+
+        # Context about the error condition
+        attr_accessor :context
 
         # A unique identifier for the request. Include this value with any error reports or support tickets
         attr_accessor :correlation_id
 
+        # A map of link names to associated URIs containing documentation about the error or recommended remediation steps
+        attr_accessor :links
+
+        # A human readable message describing the error along with remediation steps where appropriate
+        attr_accessor :message
+
         # The error category
         attr_accessor :category
 
-        # A specific category that contains more specific detail about the error
-        attr_accessor :sub_category
-
         # further information about the error
         attr_accessor :errors
 
-        # Context about the error condition
-        attr_accessor :context
-
-        # A map of link names to associated URIs containing documentation about the error or recommended remediation steps
-        attr_accessor :links
-
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'message' => :'message',
-            :'correlation_id' => :'correlationId',
-            :'category' => :'category',
             :'sub_category' => :'subCategory',
-            :'errors' => :'errors',
             :'context' => :'context',
-            :'links' => :'links'
+            :'correlation_id' => :'correlationId',
+            :'links' => :'links',
+            :'message' => :'message',
+            :'category' => :'category',
+            :'errors' => :'errors'
           }
         end
 
@@ -59,13 +59,13 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'message' => :'String',
-            :'correlation_id' => :'String',
-            :'category' => :'String',
             :'sub_category' => :'String',
-            :'errors' => :'Array<ErrorDetail>',
             :'context' => :'Hash<String, Array<String>>',
-            :'links' => :'Hash<String, String>'
+            :'correlation_id' => :'String',
+            :'links' => :'Hash<String, String>',
+            :'message' => :'String',
+            :'category' => :'String',
+            :'errors' => :'Array<ErrorDetail>'
           }
         end
 
@@ -90,53 +90,53 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'message')
-            self.message = attributes[:'message']
-          end
-
-          if attributes.key?(:'correlation_id')
-            self.correlation_id = attributes[:'correlation_id']
-          end
-
-          if attributes.key?(:'category')
-            self.category = attributes[:'category']
-          end
-
           if attributes.key?(:'sub_category')
             self.sub_category = attributes[:'sub_category']
           end
 
-          if attributes.key?(:'errors')
-            if (value = attributes[:'errors']).is_a?(Array)
-              self.errors = value
-            end
-          end
-
           if attributes.key?(:'context')
             if (value = attributes[:'context']).is_a?(Hash)
               self.context = value
             end
           end
 
+          if attributes.key?(:'correlation_id')
+            self.correlation_id = attributes[:'correlation_id']
+          end
+
           if attributes.key?(:'links')
             if (value = attributes[:'links']).is_a?(Hash)
               self.links = value
             end
           end
+
+          if attributes.key?(:'message')
+            self.message = attributes[:'message']
+          end
+
+          if attributes.key?(:'category')
+            self.category = attributes[:'category']
+          end
+
+          if attributes.key?(:'errors')
+            if (value = attributes[:'errors']).is_a?(Array)
+              self.errors = 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
-          if @message.nil?
-            invalid_properties.push('invalid value for "message", message cannot be nil.')
-          end
-
           if @correlation_id.nil?
             invalid_properties.push('invalid value for "correlation_id", correlation_id cannot be nil.')
           end
 
+          if @message.nil?
+            invalid_properties.push('invalid value for "message", message cannot be nil.')
+          end
+
           if @category.nil?
             invalid_properties.push('invalid value for "category", category cannot be nil.')
           end
@@ -147,8 +147,8 @@ module Hubspot
         # Check to see if the all the properties in the model are valid
         # @return true if the model is valid
         def valid?
-          return false if @message.nil?
           return false if @correlation_id.nil?
+          return false if @message.nil?
           return false if @category.nil?
           true
         end
@@ -158,13 +158,13 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              message == o.message &&
-              correlation_id == o.correlation_id &&
-              category == o.category &&
               sub_category == o.sub_category &&
-              errors == o.errors &&
               context == o.context &&
-              links == o.links
+              correlation_id == o.correlation_id &&
+              links == o.links &&
+              message == o.message &&
+              category == o.category &&
+              errors == o.errors
         end
 
         # @see the `==` method
@@ -176,7 +176,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [message, correlation_id, category, sub_category, errors, context, links].hash
+          [sub_category, context, correlation_id, links, message, category, errors].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/error_detail.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,29 +17,29 @@ module Hubspot
   module Cms
     module Hubdb
       class ErrorDetail
-        # A human readable message describing the error along with remediation steps where appropriate
-        attr_accessor :message
-
-        # The name of the field or parameter in which the error was found.
-        attr_accessor :_in
+        # A specific category that contains more specific detail about the error
+        attr_accessor :sub_category
 
         # The status code associated with the error detail
         attr_accessor :code
 
-        # A specific category that contains more specific detail about the error
-        attr_accessor :sub_category
+        # The name of the field or parameter in which the error was found.
+        attr_accessor :_in
 
         # Context about the error condition
         attr_accessor :context
 
+        # A human readable message describing the error along with remediation steps where appropriate
+        attr_accessor :message
+
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'message' => :'message',
-            :'_in' => :'in',
-            :'code' => :'code',
             :'sub_category' => :'subCategory',
-            :'context' => :'context'
+            :'code' => :'code',
+            :'_in' => :'in',
+            :'context' => :'context',
+            :'message' => :'message'
           }
         end
 
@@ -51,11 +51,11 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'message' => :'String',
-            :'_in' => :'String',
-            :'code' => :'String',
             :'sub_category' => :'String',
-            :'context' => :'Hash<String, Array<String>>'
+            :'code' => :'String',
+            :'_in' => :'String',
+            :'context' => :'Hash<String, Array<String>>',
+            :'message' => :'String'
           }
         end
 
@@ -80,20 +80,16 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'message')
-            self.message = attributes[:'message']
-          end
-
-          if attributes.key?(:'_in')
-            self._in = attributes[:'_in']
+          if attributes.key?(:'sub_category')
+            self.sub_category = attributes[:'sub_category']
           end
 
           if attributes.key?(:'code')
             self.code = attributes[:'code']
           end
 
-          if attributes.key?(:'sub_category')
-            self.sub_category = attributes[:'sub_category']
+          if attributes.key?(:'_in')
+            self._in = attributes[:'_in']
           end
 
           if attributes.key?(:'context')
@@ -101,6 +97,10 @@ module Hubspot
               self.context = value
             end
           end
+
+          if attributes.key?(:'message')
+            self.message = attributes[:'message']
+          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
@@ -126,11 +126,11 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              message == o.message &&
-              _in == o._in &&
-              code == o.code &&
               sub_category == o.sub_category &&
-              context == o.context
+              code == o.code &&
+              _in == o._in &&
+              context == o.context &&
+              message == o.message
         end
 
         # @see the `==` method
@@ -142,7 +142,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [message, _in, code, sub_category, context].hash
+          [sub_category, code, _in, context, message].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/foreign_id.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,17 +17,20 @@ module Hubspot
   module Cms
     module Hubdb
       class ForeignId
-        attr_accessor :id
-
+        # 
         attr_accessor :name
 
+        # 
+        attr_accessor :id
+
+        # 
         attr_accessor :type
 
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'id' => :'id',
             :'name' => :'name',
+            :'id' => :'id',
             :'type' => :'type'
           }
         end
@@ -40,8 +43,8 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'id' => :'String',
             :'name' => :'String',
+            :'id' => :'String',
             :'type' => :'String'
           }
         end
@@ -67,14 +70,14 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'id')
-            self.id = attributes[:'id']
-          end
-
           if attributes.key?(:'name')
             self.name = attributes[:'name']
           end
 
+          if attributes.key?(:'id')
+            self.id = attributes[:'id']
+          end
+
           if attributes.key?(:'type')
             self.type = attributes[:'type']
           end
@@ -84,14 +87,14 @@ module Hubspot
         # @return Array for valid properties with the reasons
         def list_invalid_properties
           invalid_properties = Array.new
-          if @id.nil?
-            invalid_properties.push('invalid value for "id", id cannot be nil.')
-          end
-
           if @name.nil?
             invalid_properties.push('invalid value for "name", name cannot be nil.')
           end
 
+          if @id.nil?
+            invalid_properties.push('invalid value for "id", id cannot be nil.')
+          end
+
           if @type.nil?
             invalid_properties.push('invalid value for "type", type cannot be nil.')
           end
@@ -102,8 +105,8 @@ module Hubspot
         # Check to see if the all the properties in the model are valid
         # @return true if the model is valid
         def valid?
-          return false if @id.nil?
           return false if @name.nil?
+          return false if @id.nil?
           return false if @type.nil?
           true
         end
@@ -113,8 +116,8 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              id == o.id &&
               name == o.name &&
+              id == o.id &&
               type == o.type
         end
 
@@ -127,7 +130,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [id, name, type].hash
+          [name, id, type].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/forward_paging.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_clone_request.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_row_v3.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,40 +17,40 @@ module Hubspot
   module Cms
     module Hubdb
       class HubDbTableRowV3
-        # The id of the table row
-        attr_accessor :id
-
-        # List of key value pairs with the column name and column value
-        attr_accessor :values
-
         # Specifies the value for `hs_path` column, which will be used as slug in the dynamic pages
         attr_accessor :path
 
-        # Specifies the value for `hs_name` column, which will be used as title in the dynamic pages
-        attr_accessor :name
+        # Timestamp at which the row is created
+        attr_accessor :created_at
 
         # Specifies the value for the column child table id
         attr_accessor :child_table_id
 
-        # Timestamp at which the row is created
-        attr_accessor :created_at
+        attr_accessor :published_at
+
+        # List of key value pairs with the column name and column value
+        attr_accessor :values
+
+        # Specifies the value for `hs_name` column, which will be used as title in the dynamic pages
+        attr_accessor :name
+
+        # The id of the table row
+        attr_accessor :id
 
         # Timestamp at which the row is updated last time
         attr_accessor :updated_at
 
-        attr_accessor :published_at
-
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'id' => :'id',
-            :'values' => :'values',
             :'path' => :'path',
-            :'name' => :'name',
-            :'child_table_id' => :'childTableId',
             :'created_at' => :'createdAt',
-            :'updated_at' => :'updatedAt',
-            :'published_at' => :'publishedAt'
+            :'child_table_id' => :'childTableId',
+            :'published_at' => :'publishedAt',
+            :'values' => :'values',
+            :'name' => :'name',
+            :'id' => :'id',
+            :'updated_at' => :'updatedAt'
           }
         end
 
@@ -62,14 +62,14 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'id' => :'String',
-            :'values' => :'Hash<String, Object>',
             :'path' => :'String',
-            :'name' => :'String',
-            :'child_table_id' => :'String',
             :'created_at' => :'Time',
-            :'updated_at' => :'Time',
-            :'published_at' => :'Time'
+            :'child_table_id' => :'String',
+            :'published_at' => :'Time',
+            :'values' => :'Hash<String, Object>',
+            :'name' => :'String',
+            :'id' => :'String',
+            :'updated_at' => :'Time'
           }
         end
 
@@ -94,8 +94,20 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'id')
-            self.id = attributes[:'id']
+          if attributes.key?(:'path')
+            self.path = attributes[:'path']
+          end
+
+          if attributes.key?(:'created_at')
+            self.created_at = attributes[:'created_at']
+          end
+
+          if attributes.key?(:'child_table_id')
+            self.child_table_id = attributes[:'child_table_id']
+          end
+
+          if attributes.key?(:'published_at')
+            self.published_at = attributes[:'published_at']
           end
 
           if attributes.key?(:'values')
@@ -104,29 +116,17 @@ module Hubspot
             end
           end
 
-          if attributes.key?(:'path')
-            self.path = attributes[:'path']
-          end
-
           if attributes.key?(:'name')
             self.name = attributes[:'name']
           end
 
-          if attributes.key?(:'child_table_id')
-            self.child_table_id = attributes[:'child_table_id']
-          end
-
-          if attributes.key?(:'created_at')
-            self.created_at = attributes[:'created_at']
+          if attributes.key?(:'id')
+            self.id = attributes[:'id']
           end
 
           if attributes.key?(:'updated_at')
             self.updated_at = attributes[:'updated_at']
           end
-
-          if attributes.key?(:'published_at')
-            self.published_at = attributes[:'published_at']
-          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
@@ -152,14 +152,14 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              id == o.id &&
-              values == o.values &&
               path == o.path &&
-              name == o.name &&
-              child_table_id == o.child_table_id &&
               created_at == o.created_at &&
-              updated_at == o.updated_at &&
-              published_at == o.published_at
+              child_table_id == o.child_table_id &&
+              published_at == o.published_at &&
+              values == o.values &&
+              name == o.name &&
+              id == o.id &&
+              updated_at == o.updated_at
         end
 
         # @see the `==` method
@@ -171,7 +171,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [id, values, path, name, child_table_id, created_at, updated_at, published_at].hash
+          [path, created_at, child_table_id, published_at, values, name, id, updated_at].hash
         end
 
         # Builds the object from hash