lockally 0.2.0 → 0.3.0

data/spec/models/{v1_templates_get200_response_spec.rb → send_email_batch200_response_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1TemplatesGet200Response
+# Unit tests for Lockally::SendEmailBatch200Response
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1TemplatesGet200Response do
-  #let(:instance) { Lockally::V1TemplatesGet200Response.new }
+describe Lockally::SendEmailBatch200Response do
+  #let(:instance) { Lockally::SendEmailBatch200Response.new }
 
-  describe 'test an instance of V1TemplatesGet200Response' do
-    it 'should create an instance of V1TemplatesGet200Response' do
+  describe 'test an instance of SendEmailBatch200Response' do
+    it 'should create an instance of SendEmailBatch200Response' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1TemplatesGet200Response)
+      #expect(instance).to be_instance_of(Lockally::SendEmailBatch200Response)
     end
   end
 

data/spec/models/{v1_send_batch_post_request_spec.rb → send_email_batch_request_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1SendBatchPostRequest
+# Unit tests for Lockally::SendEmailBatchRequest
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1SendBatchPostRequest do
-  #let(:instance) { Lockally::V1SendBatchPostRequest.new }
+describe Lockally::SendEmailBatchRequest do
+  #let(:instance) { Lockally::SendEmailBatchRequest.new }
 
-  describe 'test an instance of V1SendBatchPostRequest' do
-    it 'should create an instance of V1SendBatchPostRequest' do
+  describe 'test an instance of SendEmailBatchRequest' do
+    it 'should create an instance of SendEmailBatchRequest' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1SendBatchPostRequest)
+      #expect(instance).to be_instance_of(Lockally::SendEmailBatchRequest)
     end
   end
 

data/spec/models/{v1_send_post_request_attachments_inner_spec.rb → send_email_request_attachments_inner_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1SendPostRequestAttachmentsInner
+# Unit tests for Lockally::SendEmailRequestAttachmentsInner
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1SendPostRequestAttachmentsInner do
-  #let(:instance) { Lockally::V1SendPostRequestAttachmentsInner.new }
+describe Lockally::SendEmailRequestAttachmentsInner do
+  #let(:instance) { Lockally::SendEmailRequestAttachmentsInner.new }
 
-  describe 'test an instance of V1SendPostRequestAttachmentsInner' do
-    it 'should create an instance of V1SendPostRequestAttachmentsInner' do
+  describe 'test an instance of SendEmailRequestAttachmentsInner' do
+    it 'should create an instance of SendEmailRequestAttachmentsInner' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1SendPostRequestAttachmentsInner)
+      #expect(instance).to be_instance_of(Lockally::SendEmailRequestAttachmentsInner)
     end
   end
 

data/spec/models/{v1_send_post_request_spec.rb → send_email_request_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1SendPostRequest
+# Unit tests for Lockally::SendEmailRequest
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1SendPostRequest do
-  #let(:instance) { Lockally::V1SendPostRequest.new }
+describe Lockally::SendEmailRequest do
+  #let(:instance) { Lockally::SendEmailRequest.new }
 
-  describe 'test an instance of V1SendPostRequest' do
-    it 'should create an instance of V1SendPostRequest' do
+  describe 'test an instance of SendEmailRequest' do
+    it 'should create an instance of SendEmailRequest' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1SendPostRequest)
+      #expect(instance).to be_instance_of(Lockally::SendEmailRequest)
     end
   end
 

data/spec/models/{v1_mailboxes_email_vacation_put_request_spec.rb → set_vacation_responder_request_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1MailboxesEmailVacationPutRequest
+# Unit tests for Lockally::SetVacationResponderRequest
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1MailboxesEmailVacationPutRequest do
-  #let(:instance) { Lockally::V1MailboxesEmailVacationPutRequest.new }
+describe Lockally::SetVacationResponderRequest do
+  #let(:instance) { Lockally::SetVacationResponderRequest.new }
 
-  describe 'test an instance of V1MailboxesEmailVacationPutRequest' do
-    it 'should create an instance of V1MailboxesEmailVacationPutRequest' do
+  describe 'test an instance of SetVacationResponderRequest' do
+    it 'should create an instance of SetVacationResponderRequest' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1MailboxesEmailVacationPutRequest)
+      #expect(instance).to be_instance_of(Lockally::SetVacationResponderRequest)
     end
   end
 

data/spec/models/simulated_inbound_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::SimulatedInbound
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::SimulatedInbound do
+  #let(:instance) { Lockally::SimulatedInbound.new }
+
+  describe 'test an instance of SimulatedInbound' do
+    it 'should create an instance of SimulatedInbound' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::SimulatedInbound)
+    end
+  end
+
+  describe 'test attribute "thread_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "message_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "annotations"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/{v1_inboxes_mailbox_messages_post_request_spec.rb → start_conversation_request_spec.rb}

@@ -14,16 +14,16 @@ require 'spec_helper'
 require 'json'
 require 'date'
 
-# Unit tests for Lockally::V1InboxesMailboxMessagesPostRequest
+# Unit tests for Lockally::StartConversationRequest
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe Lockally::V1InboxesMailboxMessagesPostRequest do
-  #let(:instance) { Lockally::V1InboxesMailboxMessagesPostRequest.new }
+describe Lockally::StartConversationRequest do
+  #let(:instance) { Lockally::StartConversationRequest.new }
 
-  describe 'test an instance of V1InboxesMailboxMessagesPostRequest' do
-    it 'should create an instance of V1InboxesMailboxMessagesPostRequest' do
+  describe 'test an instance of StartConversationRequest' do
+    it 'should create an instance of StartConversationRequest' do
       # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Lockally::V1InboxesMailboxMessagesPostRequest)
+      #expect(instance).to be_instance_of(Lockally::StartConversationRequest)
     end
   end
 

data/spec/models/thread_classification_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ThreadClassification
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ThreadClassification do
+  #let(:instance) { Lockally::ThreadClassification.new }
+
+  describe 'test an instance of ThreadClassification' do
+    it 'should create an instance of ThreadClassification' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ThreadClassification)
+    end
+  end
+
+  describe 'test attribute "thread_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "cached"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "classification"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/thread_list_spec.rb

@@ -0,0 +1,42 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ThreadList
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ThreadList do
+  #let(:instance) { Lockally::ThreadList.new }
+
+  describe 'test an instance of ThreadList' do
+    it 'should create an instance of ThreadList' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ThreadList)
+    end
+  end
+
+  describe 'test attribute "mailbox"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "threads"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/thread_message_body_all_of_body_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ThreadMessageBodyAllOfBody
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ThreadMessageBodyAllOfBody do
+  #let(:instance) { Lockally::ThreadMessageBodyAllOfBody.new }
+
+  describe 'test an instance of ThreadMessageBodyAllOfBody' do
+    it 'should create an instance of ThreadMessageBodyAllOfBody' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ThreadMessageBodyAllOfBody)
+    end
+  end
+
+  describe 'test attribute "text"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "html"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "truncated"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/thread_message_body_spec.rb

@@ -0,0 +1,112 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ThreadMessageBody
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ThreadMessageBody do
+  #let(:instance) { Lockally::ThreadMessageBody.new }
+
+  describe 'test an instance of ThreadMessageBody' do
+    it 'should create an instance of ThreadMessageBody' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ThreadMessageBody)
+    end
+  end
+
+  describe 'test attribute "id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "direction"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["inbound", "outbound"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.direction = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "rfc_message_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "in_reply_to"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "subject"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "from"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "to"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "snippet"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "has_attachments"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "attachments"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "annotations"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "received_at"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "body"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/thread_message_spec.rb

@@ -0,0 +1,106 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ThreadMessage
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ThreadMessage do
+  #let(:instance) { Lockally::ThreadMessage.new }
+
+  describe 'test an instance of ThreadMessage' do
+    it 'should create an instance of ThreadMessage' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ThreadMessage)
+    end
+  end
+
+  describe 'test attribute "id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "direction"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["inbound", "outbound"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.direction = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "rfc_message_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "in_reply_to"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "subject"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "from"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "to"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "snippet"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "has_attachments"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "attachments"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "annotations"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "received_at"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/thread_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`, or `lk_test_<...>` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`.  The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::Thread
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::Thread do
+  #let(:instance) { Lockally::Thread.new }
+
+  describe 'test an instance of Thread' do
+    it 'should create an instance of Thread' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::Thread)
+    end
+  end
+
+  describe 'test attribute "thread"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "mailbox"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "messages"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end