zyphr 0.1.30 → 0.1.31

data/spec/models/get_domain200_response_meta_spec.rb

@@ -1,36 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::GetDomain200ResponseMeta
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::GetDomain200ResponseMeta do
-  let(:instance) { Zyphr::GetDomain200ResponseMeta.new }
-
-  describe 'test an instance of GetDomain200ResponseMeta' do
-    it 'should create an instance of GetDomain200ResponseMeta' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::GetDomain200ResponseMeta)
-    end
-  end
-
-  describe 'test attribute "request_id"' 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/get_domain200_response_spec.rb

@@ -1,42 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::GetDomain200Response
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::GetDomain200Response do
-  let(:instance) { Zyphr::GetDomain200Response.new }
-
-  describe 'test an instance of GetDomain200Response' do
-    it 'should create an instance of GetDomain200Response' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::GetDomain200Response)
-    end
-  end
-
-  describe 'test attribute "data"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "meta"' 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/verification_status_response_data_spec.rb

@@ -1,82 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::VerificationStatusResponseData
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::VerificationStatusResponseData do
-  let(:instance) { Zyphr::VerificationStatusResponseData.new }
-
-  describe 'test an instance of VerificationStatusResponseData' do
-    it 'should create an instance of VerificationStatusResponseData' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::VerificationStatusResponseData)
-    end
-  end
-
-  describe 'test attribute "domain_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 "domain"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "status"' 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', ["pending", "verifying", "verified", "failed"])
-      # validator.allowable_values.each do |value|
-      #   expect { instance.status = value }.not_to raise_error
-      # end
-    end
-  end
-
-  describe 'test attribute "records_verified"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "records_total"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "progress"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "dns_records"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "last_checked_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/verification_status_response_spec.rb

@@ -1,42 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::VerificationStatusResponse
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::VerificationStatusResponse do
-  let(:instance) { Zyphr::VerificationStatusResponse.new }
-
-  describe 'test an instance of VerificationStatusResponse' do
-    it 'should create an instance of VerificationStatusResponse' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::VerificationStatusResponse)
-    end
-  end
-
-  describe 'test attribute "data"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "meta"' 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/verify_domain_response_data_spec.rb

@@ -1,58 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::VerifyDomainResponseData
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::VerifyDomainResponseData do
-  let(:instance) { Zyphr::VerifyDomainResponseData.new }
-
-  describe 'test an instance of VerifyDomainResponseData' do
-    it 'should create an instance of VerifyDomainResponseData' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::VerifyDomainResponseData)
-    end
-  end
-
-  describe 'test attribute "job_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 "domain_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 "domain"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "status"' 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', ["verifying"])
-      # validator.allowable_values.each do |value|
-      #   expect { instance.status = value }.not_to raise_error
-      # end
-    end
-  end
-
-end

data/spec/models/verify_domain_response_spec.rb

@@ -1,42 +0,0 @@
-=begin
-#Zyphr API
-
-#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
-
-The version of the OpenAPI document: 1.0.0
-Contact: support@zyphr.dev
-Generated by: https://openapi-generator.tech
-Generator version: 7.12.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for Zyphr::VerifyDomainResponse
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe Zyphr::VerifyDomainResponse do
-  let(:instance) { Zyphr::VerifyDomainResponse.new }
-
-  describe 'test an instance of VerifyDomainResponse' do
-    it 'should create an instance of VerifyDomainResponse' do
-      # uncomment below to test the instance creation
-      #expect(instance).to be_instance_of(Zyphr::VerifyDomainResponse)
-    end
-  end
-
-  describe 'test attribute "data"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-  describe 'test attribute "meta"' do
-    it 'should work' do
-      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-    end
-  end
-
-end