explicit_activerecord 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f9d1ed0101b826fc591cb78e46eef4f297754b42dba7fa3e2ee3c8342082ddd3
-  data.tar.gz: c52614803edb50bd57da611fe5e19507f68199de979c314ad34c32f6495bf1e2
+  metadata.gz: fed051d27a951002f71dd499cef812bd97b4e4e62ddfc819ba2bef791c98658f
+  data.tar.gz: f3b11237b4b2e90b72fd2c5fae9a95c069d007a2375b5b76f2a7879980a61062
 SHA512:
-  metadata.gz: 968de86a11cd97fcf632c2d9d4d043d44eda52bda87ccf1e55a944afdd1feeaa95e9caaca75027a8047c51be5c3bc01675502f128a29bdaf7fbdcc3fdeac56d5
-  data.tar.gz: d41aeb3ecd8d4b32492f2d71253ace7884883a436c23307cfe13040b4dd98fd59dee0595318cb7cb3c0a4c0fb7ffd1e5368d6dcd7ac214e8bd1e7e14dc79845d
+  metadata.gz: 8676f04c92c9dc752b4998c000944d1e8021b50cd9fad176147c5c784c39e2710d10ff6f41fd9a893ea99d8da4b0b643eec598d7138cf2e427d1fc64f66d7faa
+  data.tar.gz: f9ff60de72bb7b1ef490faa1bb90469f69d118e4ef41458267ad1380dd20009882e312289edc0ada7d0757aa0faf6fba3c18af56db68ec0b9aa2dd9b47ddb13f

data/README.md

@@ -45,7 +45,7 @@ Once your model is configured correctly to use `ExplicitActiveRecord::Persistenc
 ### Incremental
 `ExplicitActiveRecord::Persistence` is *incremental*. This means that you can include `ExplicitActiveRecord::Persistence`, and specify a *non-raising* behavior when the model is persisted implicitly, and use your logs or bug tracking system to find places where the model is implicitly raising, without breaking production. [See the `README` for `deprecation_helper` for more information on this](https://github.com/Gusto/deprecation_helper/blob/main/README.md).
 
-### Usage 
+### Usage
 The first step is to `include ExplicitActiveRecord::Persistence` in your models:
 
 Secondly, you'll need to configure `dangerous_update_behaviors` (see the `deprecation_helper` gem for more info).
@@ -91,7 +91,7 @@ Note that you cannot pass in a relation to `with_explicit_persistence_for` — o
 It is *not* recommended to use this dynamically, such as:
 ```ruby
 # Don't do this!
-self.class.with_explicit_persistence_forinstance) do
+self.class.with_explicit_persistence_for(instance) do
   instance.save!
 end
 ```
@@ -102,23 +102,23 @@ You can specify multiple behaviors to invoke when the model is updated implicitl
 
 Note that by default, `ExplicitActiveRecord` uses the global configuration for `DeprecationHelper`. If your project has already configured `DeprecationHelper`, using:
 ```ruby
-DeprecationHelper.configure { |config| config.deprecation_strategies = [...] })
+DeprecationHelper.configure { |config| config.deprecation_strategies = [...] }
 ```
 then `ExplicitActiveRecord` will use the global configuration.
 
 ### How it works
-When a client calls `my_model.save!` or `my_model.update!` without using the explicit persistence wrapper, `ExplicitActiveRecord::Persistence` will invoke `DeprecationHelper` with whatever deprecation strategies your model is configured with. 
+When a client calls `my_model.save!` or `my_model.update!` without using the explicit persistence wrapper, `ExplicitActiveRecord::Persistence` will invoke `DeprecationHelper` with whatever deprecation strategies your model is configured with.
 
 
-## ExplicitActiveRecord::NoDbAccess 
+## ExplicitActiveRecord::NoDbAccess
 `ExplicitActiveRecord::NoDbAccess` has a single public method to restrict the use of the database.
 
-Once your class or module is configured correctly to use `ExplicitActiveRecord::NoDbAccess`, you will not be able to use the database within the `no_db_access` block. 
+Once your class or module is configured correctly to use `ExplicitActiveRecord::NoDbAccess`, you will not be able to use the database within the `no_db_access` block.
 
 ### Incremental
 Note that unlike `ExplicitActiveRecord::Persistence`, `ExplicitActiveRecord::NoDbAccess` is NOT *incremental*. This means that using the DB within one of these blocks *will raise*. If you're interested in allowing `no_db_access` to behave like `Persistence`, please file an issue. It is recommended to use `NoDbAccess` in new code where you are very confident your code should not be using the DB.
 
-### Usage 
+### Usage
 The first step is to `include ExplicitActiveRecord::NoDbAccess` in your module or class.
 
 Then, you can use the `no_db_access` block.
@@ -127,7 +127,7 @@ All together, this looks like this:
 ```ruby
 class MyClass # can also be a module
   include ExplicitActiveRecord::NoDbAccess
-  
+
   # Class method
   def self.my_method
     no_db_access do

data/lib/explicit_activerecord/no_db_access.rb

@@ -1,4 +1,4 @@
-# typed: false
+# typed: true
 
 # this is meant to allow callers to write code like this:
 #   model = MyModel.find

data/lib/explicit_activerecord.rb

@@ -1,3 +1,4 @@
+# typed: strict
 require 'sorbet-runtime'
 require 'active_support/concern'
 require 'deprecation_helper'

metadata

@@ -1,27 +1,27 @@
 --- !ruby/object:Gem::Specification
 name: explicit_activerecord
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Alex Evanczuk
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-02-23 00:00:00.000000000 Z
+date: 2025-09-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sorbet-runtime
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: 0.5.6293
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: 0.5.6293
 - !ruby/object:Gem::Dependency
@@ -98,16 +98,16 @@ dependencies:
   name: sorbet
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.5.6293
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.5.6293
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
@@ -122,7 +122,21 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description: 
+- !ruby/object:Gem::Dependency
+  name: tapioca
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description:
 email:
 - alex.evanczuk@gusto.com
 executables: []
@@ -134,10 +148,11 @@ files:
 - lib/explicit_activerecord.rb
 - lib/explicit_activerecord/no_db_access.rb
 - lib/explicit_activerecord/persistence.rb
-homepage: 
-licenses: []
+homepage: https://github.com/Gusto/explicit_activerecord
+licenses:
+- MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -145,15 +160,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: '3.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
-signing_key: 
+rubygems_version: 3.4.19
+signing_key:
 specification_version: 4
 summary: This is a gem for using ActiveRecord more explicitly.
 test_files: []