chore: update SDK settings

Author: stainless-app[bot]

.rubocop.yml

@@ -40,9 +40,9 @@ Layout/LineLength:
   AllowedPatterns:
     - "^\\s*#.*$"
     - ^require(_relative)?
-    - "Tilda::Internal::Type::BaseModel$"
+    - "TildaRuby::Internal::Type::BaseModel$"
     - "^\\s*[A-Z0-9_]+ = :"
-    - "Tilda::(Models|Resources|Test)::"
+    - "TildaRuby::(Models|Resources|Test)::"
   Max: 110
 
 Layout/MultilineArrayLineBreaks:

.solargraph.yml

@@ -5,7 +5,7 @@ include:
   - 'Rakefile'
   - 'examples/**/*.rb'
   - 'lib/**/*.rb'
-  - 'test/tilda/resource_namespaces.rb'
-  - 'test/tilda/test_helper.rb'
+  - 'test/tilda_ruby/resource_namespaces.rb'
+  - 'test/tilda_ruby/test_helper.rb'
 exclude:
   - 'rbi/**/*'

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 7
 openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/hexlet%2Ftilda-d06441794bcf349b37439e4084aa5accb40ad16d553d5013cd33b9379f183dc1.yml
 openapi_spec_hash: 231389205a35d2d6c56bd1cac4091e81
-config_hash: bd8285a8057799f62d48a60cf5a204cf
+config_hash: 02a97d1e54040f9bd1eeef26fc735da7

CONTRIBUTING.md

@@ -14,7 +14,7 @@ This will install all the required dependencies.
 
 ## Modifying/Adding code
 
-Most of the SDK is generated code. Modifications to code will be persisted between generations, but may result in merge conflicts between manual patches and changes from the generator. The generator will never modify the contents of `lib/tilda/helpers/` and `examples/` directory.
+Most of the SDK is generated code. Modifications to code will be persisted between generations, but may result in merge conflicts between manual patches and changes from the generator. The generator will never modify the contents of `lib/tilda_ruby/helpers/` and `examples/` directory.
 
 ## Adding and running examples
 
@@ -24,7 +24,7 @@ All files in the `examples/` directory are not modified by the generator and can
 #!/usr/bin/env ruby
 # frozen_string_literal: true
 
-require_relative "../lib/tilda"
+require_relative "../lib/tilda_ruby"
 
 # ...
 ```
@@ -43,7 +43,7 @@ If you’d like to use the repository from source, you can either install from g
 To install via git in your `Gemfile`:
 
 ```ruby
-gem "tilda", git: "https://github.com/Hexlet/tilda-ruby"
+gem "tilda-ruby", git: "https://github.com/Hexlet/tilda-ruby"
 ```
 
 Alternatively, reference local copy of the repo:
@@ -53,7 +53,7 @@ $ git clone -- 'https://github.com/Hexlet/tilda-ruby' '<path-to-repo>'
 ```
 
 ```ruby
-gem "tilda", path: "<path-to-repo>"
+gem "tilda-ruby", path: "<path-to-repo>"
 ```
 
 ## Running commands

Gemfile.lock

@@ -11,7 +11,7 @@ GIT
 PATH
   remote: .
   specs:
-    tilda (0.0.1)
+    tilda-ruby (0.0.1)
       cgi
       connection_pool
 
@@ -219,7 +219,7 @@ DEPENDENCIES
   syntax_tree
   syntax_tree-rbs!
   tapioca
-  tilda!
+  tilda-ruby!
   webmock
   webrick
   yard

README.md

@@ -6,7 +6,7 @@ It is generated with [Stainless](https://www.stainless.com/).
 
 ## Documentation
 
-Documentation for releases of this gem can be found [on RubyDoc](https://gemdocs.org/gems/tilda).
+Documentation for releases of this gem can be found [on RubyDoc](https://gemdocs.org/gems/tilda-ruby).
 
 ## Installation
 
@@ -15,7 +15,7 @@ To use this gem, install via Bundler by adding the following to your application
 <!-- x-release-please-start-version -->
 
 ```ruby
-gem "tilda", "~> 0.0.1"
+gem "tilda-ruby", "~> 0.0.1"
 ```
 
 <!-- x-release-please-end -->
@@ -24,9 +24,9 @@ gem "tilda", "~> 0.0.1"
 
 ```ruby
 require "bundler/setup"
-require "tilda"
+require "tilda_ruby"
 
-tilda = Tilda::Client.new(
+tilda = TildaRuby::Client.new(
   api_key: ENV["TILDA_API_KEY"] # This is the default and can be omitted
 )
 
@@ -37,17 +37,17 @@ puts(getpage)
 
 ### Handling errors
 
-When the library is unable to connect to the API, or if the API returns a non-success status code (i.e., 4xx or 5xx response), a subclass of `Tilda::Errors::APIError` will be thrown:
+When the library is unable to connect to the API, or if the API returns a non-success status code (i.e., 4xx or 5xx response), a subclass of `TildaRuby::Errors::APIError` will be thrown:
 
 ```ruby
 begin
   getpage = tilda.getpage.retrieve(pageid: "REPLACE_ME")
-rescue Tilda::Errors::APIConnectionError => e
+rescue TildaRuby::Errors::APIConnectionError => e
   puts("The server could not be reached")
   puts(e.cause)  # an underlying Exception, likely raised within `net/http`
-rescue Tilda::Errors::RateLimitError => e
+rescue TildaRuby::Errors::RateLimitError => e
   puts("A 429 status code was received; we should back off a bit.")
-rescue Tilda::Errors::APIStatusError => e
+rescue TildaRuby::Errors::APIStatusError => e
   puts("Another non-200-range status code was received")
   puts(e.status)
 end
@@ -79,7 +79,7 @@ You can use the `max_retries` option to configure or disable this:
 
 ```ruby
 # Configure the default for all requests:
-tilda = Tilda::Client.new(
+tilda = TildaRuby::Client.new(
   max_retries: 0 # default is 2
 )
 
@@ -93,23 +93,23 @@ By default, requests will time out after 60 seconds. You can use the timeout opt
 
 ```ruby
 # Configure the default for all requests:
-tilda = Tilda::Client.new(
+tilda = TildaRuby::Client.new(
   timeout: nil # default is 60
 )
 
 # Or, configure per-request:
 tilda.getpage.retrieve(pageid: "REPLACE_ME", request_options: {timeout: 5})
 ```
 
-On timeout, `Tilda::Errors::APITimeoutError` is raised.
+On timeout, `TildaRuby::Errors::APITimeoutError` is raised.
 
 Note that requests that time out are retried by default.
 
 ## Advanced concepts
 
 ### BaseModel
 
-All parameter and response objects inherit from `Tilda::Internal::Type::BaseModel`, which provides several conveniences, including:
+All parameter and response objects inherit from `TildaRuby::Internal::Type::BaseModel`, which provides several conveniences, including:
 
 1. All fields, including unknown ones, are accessible with `obj[:prop]` syntax, and can be destructured with `obj => {prop: prop}` or pattern-matching syntax.
 
@@ -161,9 +161,9 @@ response = client.request(
 
 ### Concurrency & connection pooling
 
-The `Tilda::Client` instances are threadsafe, but are only are fork-safe when there are no in-flight HTTP requests.
+The `TildaRuby::Client` instances are threadsafe, but are only are fork-safe when there are no in-flight HTTP requests.
 
-Each instance of `Tilda::Client` has its own HTTP connection pool with a default size of 99. As such, we recommend instantiating the client once per application in most settings.
+Each instance of `TildaRuby::Client` has its own HTTP connection pool with a default size of 99. As such, we recommend instantiating the client once per application in most settings.
 
 When all available connections from the pool are checked out, requests wait for a new connection to become available, with queue time counting towards the request timeout.
 
@@ -186,7 +186,7 @@ Or, equivalently:
 tilda.getpage.retrieve(pageid: "REPLACE_ME")
 
 # You can also splat a full Params class:
-params = Tilda::GetpageRetrieveParams.new(pageid: "REPLACE_ME")
+params = TildaRuby::GetpageRetrieveParams.new(pageid: "REPLACE_ME")
 tilda.getpage.retrieve(**params)
 ```
 

Rakefile

@@ -162,7 +162,7 @@ multitask(:"build:gem") do
     sig/*
   GLOB
 
-  sh(*%w[gem build -- tilda.gemspec])
+  sh(*%w[gem build -- tilda_ruby.gemspec])
   rm_rf(ignore_file)
 end