consul 1.3.1 → 1.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7d56978b19324d537eb1380dd0435e7a9dca4b4c8e7195f0e4e649ad6baa3065
-  data.tar.gz: ebe94441887929eae46422dbc6974e5b71da7e41fba2d0005f9ed650f471b14e
+  metadata.gz: ee6dc0b253298727f44d5dfb975ab428349401e005b960156090591d930bfcf1
+  data.tar.gz: aeab801a53fd4c287736fb6f17397c24507b214fa77d803f6c1e54aa4d8dce50
 SHA512:
-  metadata.gz: a85d9db39a349fc55768bc54d87c198f41fd9bdbd6f254ed9e9c75c5783c3809e4f08f797407894c5f6cd39bfbb8fb0bd9d2428756dcb0997ab158d3f1fc1af9
-  data.tar.gz: e74d092a626238d63b605db9da653ef63dbf08fabca8d18dfff25602fc25771a32733bb4c22adc749703d8b53c50d6aeff46e88ed9279f5afb4cae23148b728b
+  metadata.gz: e6480d378cb267f8bd0e018f1b5f47f3d815aad2b7d2a0477042564fb3fce5fab348b93f217957e278d7b299813960a8eeea0ca832a35ca1d23a87335d10dae1
+  data.tar.gz: 60b20e4cfc85b430502fd6ff28b2403a152710b7c1ee1c56fa1121c162a079db4b1b18a8ac71c6b87cf8f94abb6be8afee38f35d0170187ad264e4a78d019e0c

data/.github/workflows/test.yml

@@ -3,10 +3,10 @@ name: Tests
 on:
   push:
     branches:
-    - master
+      - master
   pull_request:
     branches:
-    - master
+      - master
 jobs:
   test:
     runs-on: ubuntu-20.04
@@ -14,29 +14,31 @@ jobs:
       fail-fast: false
       matrix:
         include:
-        - ruby: 2.5.3
-          gemfile: Gemfile.5-2
-        - ruby: 2.5.3
-          gemfile: Gemfile.6-1
-        - ruby: 2.7.3
-          gemfile: Gemfile.6-1
-        - ruby: 2.7.3
-          gemfile: Gemfile.7-0
-        - ruby: 3.2.0
-          gemfile: Gemfile.6-1
-        - ruby: 3.2.0
-          gemfile: Gemfile.7-0
+          - ruby: 2.5.3
+            gemfile: Gemfile.5-2
+          - ruby: 2.5.3
+            gemfile: Gemfile.6-1
+          - ruby: 2.7.3
+            gemfile: Gemfile.6-1
+          - ruby: 2.7.3
+            gemfile: Gemfile.7-0
+          - ruby: 3.2.0
+            gemfile: Gemfile.6-1
+          - ruby: 3.2.0
+            gemfile: Gemfile.7-0
+          - ruby: 3.3.4
+            gemfile: Gemfile.7-1
     env:
       BUNDLE_GEMFILE: "${{ matrix.gemfile }}"
     steps:
-    - uses: actions/checkout@v2
-    - name: Install ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: "${{ matrix.ruby }}"
-    - name: Bundle
-      run: |
-        gem install bundler:1.17.3
-        bundle install --no-deployment
-    - name: Run tests
-      run: bundle exec rspec
+      - uses: actions/checkout@v2
+      - name: Install ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: "${{ matrix.ruby }}"
+      - name: Bundle
+        run: |
+          gem install bundler:1.17.3
+          bundle install --no-deployment
+      - name: Run tests
+        run: bundle exec rspec

data/.ruby-version

@@ -1 +1 @@
-3.2.0
+3.3.4

data/CHANGELOG.md

@@ -9,6 +9,12 @@ This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html
 
 ### Compatible changes
 
+## 1.3.2 - 2023-08-27
+
+### Compatible changes
+
+- Hook into railties correctly
+
 ## 1.3.1 - 2023-02-28
 
 ### Compatible changes

data/Gemfile

@@ -1 +1 @@
-Gemfile.7-0
+Gemfile.7-1

data/Gemfile.5-2.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    consul (1.3.1)
+    consul (1.3.2)
       activerecord (>= 3.2)
       activesupport (>= 3.2)
       edge_rider (>= 0.3.0)

data/Gemfile.6-1.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    consul (1.3.1)
+    consul (1.3.2)
       activerecord (>= 3.2)
       activesupport (>= 3.2)
       edge_rider (>= 0.3.0)

data/Gemfile.7-0.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    consul (1.3.1)
+    consul (1.3.2)
       activerecord (>= 3.2)
       activesupport (>= 3.2)
       edge_rider (>= 0.3.0)

data/Gemfile.7-1

@@ -0,0 +1,17 @@
+source 'https://rubygems.org'
+
+# Runtime dependencies
+gem 'railties', '>= 7.0.1'
+gem 'assignable_values'
+
+# Development dependencies
+gem 'rspec'
+gem 'rspec-rails'
+gem 'rspec_candy'
+gem 'shoulda-matchers'
+gem 'sqlite3', "~> 1.7"
+gem 'database_cleaner'
+gem 'gemika', '>= 0.8.1'
+
+# Gem under test
+gem 'consul', :path => '.'

data/Gemfile.7-1.lock

@@ -0,0 +1,167 @@
+PATH
+  remote: .
+  specs:
+    consul (1.3.2)
+      activerecord (>= 3.2)
+      activesupport (>= 3.2)
+      edge_rider (>= 0.3.0)
+      memoized (>= 1.0.2)
+      railties (>= 3.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actionpack (7.1.3.4)
+      actionview (= 7.1.3.4)
+      activesupport (= 7.1.3.4)
+      nokogiri (>= 1.8.5)
+      racc
+      rack (>= 2.2.4)
+      rack-session (>= 1.0.1)
+      rack-test (>= 0.6.3)
+      rails-dom-testing (~> 2.2)
+      rails-html-sanitizer (~> 1.6)
+    actionview (7.1.3.4)
+      activesupport (= 7.1.3.4)
+      builder (~> 3.1)
+      erubi (~> 1.11)
+      rails-dom-testing (~> 2.2)
+      rails-html-sanitizer (~> 1.6)
+    activemodel (7.1.3.4)
+      activesupport (= 7.1.3.4)
+    activerecord (7.1.3.4)
+      activemodel (= 7.1.3.4)
+      activesupport (= 7.1.3.4)
+      timeout (>= 0.4.0)
+    activesupport (7.1.3.4)
+      base64
+      bigdecimal
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      connection_pool (>= 2.2.5)
+      drb
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      mutex_m
+      tzinfo (~> 2.0)
+    assignable_values (1.0.0)
+      activerecord (>= 2.3)
+    base64 (0.2.0)
+    bigdecimal (3.1.8)
+    builder (3.3.0)
+    concurrent-ruby (1.3.3)
+    connection_pool (2.4.1)
+    crass (1.0.6)
+    database_cleaner (2.0.2)
+      database_cleaner-active_record (>= 2, < 3)
+    database_cleaner-active_record (2.2.0)
+      activerecord (>= 5.a)
+      database_cleaner-core (~> 2.0.0)
+    database_cleaner-core (2.0.1)
+    diff-lcs (1.5.1)
+    drb (2.2.1)
+    edge_rider (2.3.0)
+      activerecord (>= 3.2)
+    erubi (1.13.0)
+    gemika (0.8.3)
+    i18n (1.14.5)
+      concurrent-ruby (~> 1.0)
+    io-console (0.7.2)
+    irb (1.14.0)
+      rdoc (>= 4.0.0)
+      reline (>= 0.4.2)
+    loofah (2.22.0)
+      crass (~> 1.0.2)
+      nokogiri (>= 1.12.0)
+    memoized (1.1.1)
+    mini_portile2 (2.8.7)
+    minitest (5.24.1)
+    mutex_m (0.2.0)
+    nokogiri (1.16.6)
+      mini_portile2 (~> 2.8.2)
+      racc (~> 1.4)
+    psych (5.1.2)
+      stringio
+    racc (1.8.0)
+    rack (3.1.7)
+    rack-session (2.0.0)
+      rack (>= 3.0.0)
+    rack-test (2.1.0)
+      rack (>= 1.3)
+    rackup (2.1.0)
+      rack (>= 3)
+      webrick (~> 1.8)
+    rails-dom-testing (2.2.0)
+      activesupport (>= 5.0.0)
+      minitest
+      nokogiri (>= 1.6)
+    rails-html-sanitizer (1.6.0)
+      loofah (~> 2.21)
+      nokogiri (~> 1.14)
+    railties (7.1.3.4)
+      actionpack (= 7.1.3.4)
+      activesupport (= 7.1.3.4)
+      irb
+      rackup (>= 1.0.0)
+      rake (>= 12.2)
+      thor (~> 1.0, >= 1.2.2)
+      zeitwerk (~> 2.6)
+    rake (13.2.1)
+    rdoc (6.7.0)
+      psych (>= 4.0.0)
+    reline (0.5.9)
+      io-console (~> 0.5)
+    rspec (3.13.0)
+      rspec-core (~> 3.13.0)
+      rspec-expectations (~> 3.13.0)
+      rspec-mocks (~> 3.13.0)
+    rspec-core (3.13.0)
+      rspec-support (~> 3.13.0)
+    rspec-expectations (3.13.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-mocks (3.13.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-rails (6.1.3)
+      actionpack (>= 6.1)
+      activesupport (>= 6.1)
+      railties (>= 6.1)
+      rspec-core (~> 3.13)
+      rspec-expectations (~> 3.13)
+      rspec-mocks (~> 3.13)
+      rspec-support (~> 3.13)
+    rspec-support (3.13.1)
+    rspec_candy (0.5.1)
+      rspec
+      sneaky-save
+    shoulda-matchers (6.2.0)
+      activesupport (>= 5.2.0)
+    sneaky-save (0.1.3)
+      activerecord (>= 3.2.0)
+    sqlite3 (1.7.3)
+      mini_portile2 (~> 2.8.0)
+    stringio (3.1.1)
+    thor (1.3.1)
+    timeout (0.4.1)
+    tzinfo (2.0.6)
+      concurrent-ruby (~> 1.0)
+    webrick (1.8.1)
+    zeitwerk (2.6.16)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  assignable_values
+  consul!
+  database_cleaner
+  gemika (>= 0.8.1)
+  railties (>= 7.0.1)
+  rspec
+  rspec-rails
+  rspec_candy
+  shoulda-matchers
+  sqlite3 (~> 1.7)
+
+BUNDLED WITH
+   2.5.15

data/Gemfile.lock

@@ -1 +1 @@
-Gemfile.7-0.lock
+Gemfile.7-1.lock

data/README.md

@@ -1,19 +1,15 @@
-Consul — A next gen authorization solution
-==========================================
+# Consul — A next gen authorization solution
 
 [![Tests](https://github.com/makandra/consul/workflows/Tests/badge.svg)](https://github.com/makandra/consul/actions) [![Code Climate](https://codeclimate.com/github/makandra/consul.png)](https://codeclimate.com/github/makandra/consul)
 
-
-Consul is an authorization solution for Ruby on Rails where you describe *sets of accessible things* to control what a user can see or edit.
+Consul is an authorization solution for Ruby on Rails where you describe _sets of accessible things_ to control what a user can see or edit.
 
 We have used Consul in combination with [assignable_values](https://github.com/makandra/assignable_values) to solve a variety of authorization requirements ranging from boring to bizarre.
 Also see our crash course video: [Solving bizare authorization requirements with Rails](http://bizarre-authorization.talks.makandra.com/).
 
-Consul is tested with Rails 5.2, 6.1 and 7.0 on Ruby 2.5, 2.7 and 3.0 (only if supported, for each Ruby/Rails combination). If you need support for Rails 3.2, please use [v0.13.2](https://github.com/makandra/consul/tree/v0.13.2).
-
+Consul is tested with Rails 5.2, 6.1, 7.0, 7.1 on Ruby 2.5, 2.7, 3.2, 3.3 (only if supported, for each Ruby/Rails combination). If you need support for Rails 3.2, please use [v0.13.2](https://github.com/makandra/consul/tree/v0.13.2).
 
-Describing access to your application
--------------------------------------
+## Describing access to your application
 
 You describe access to your application by putting a `Power` model into `app/models/power.rb`.
 Inside your `Power` you can talk about what is accessible for the current user, e.g.
@@ -51,10 +47,8 @@ There are no restrictions on the name or constructor arguments of this class.
 
 You can deposit all kinds of objects in your power. See the sections below for details.
 
-
 ### Scope powers (relations)
 
-
 A typical use case in a Rails application is to restrict access to your ActiveRecord models. For example:
 
 - Anonymous visitors may only see public posts
@@ -111,13 +105,10 @@ power.note!(Note.last) # => raises Consul::Powerless unless the given Note is in
 
 See our crash course video [Solving bizare authorization requirements with Rails](http://bizarre-authorization.talks.makandra.com/) for many different use cases you can cover with this pattern.
 
-
-
 ### Defining different powers for different actions
 
 If you have different access rights for e.g. viewing or updating posts, simply use different powers:
 
-
 ```rb
 class Power
   ...
@@ -139,8 +130,6 @@ end
 
 There is also a [shortcut to map different powers to RESTful controller actions](#protect-entry-into-controller-actions).
 
-
-
 ### Boolean powers
 
 Boolean powers are useful to control access to stuff that doesn't live in the database:
@@ -164,7 +153,6 @@ power.dashboard? # => true
 power.dashboard! # => raises Consul::Powerless unless Power#dashboard? returns true
 ```
 
-
 ### Powers that give no access at all
 
 Note that there is a difference between having access to an empty list of records, and having no access at all.
@@ -194,8 +182,6 @@ power.user?(User.last) # => returns false
 power.user!(User.last) # => raises Consul::Powerless
 ```
 
-
-
 ### Powers that only check a given object
 
 Sometimes it is not convenient to define powers as a collection or scope (relation).
@@ -203,7 +189,6 @@ Sometimes you only want to store a method that checks whether a given object is
 
 To do so, simply define a power that ends in a question mark:
 
-
 ```rb
 class Power
   ...
@@ -223,7 +208,6 @@ power.updatable_post?(Post.last) # return true if the author of the post is @use
 power.updatable_post!(Post.last) # raises Consul::Powerless unless the author of the post is @user
 ```
 
-
 ### Other types of powers
 
 A power can return any type of object. For instance, you often want to return an array:
@@ -254,7 +238,6 @@ power.assignable_note_state?('published') # => returns false
 power.assignable_note_state!('published') # => raises Consul::Powerless
 ```
 
-
 ### Defining multiple powers at once
 
 You can define multiple powers at once by giving multiple power names:
@@ -270,7 +253,6 @@ class Power
 end
 ```
 
-
 ### Powers that require context (arguments)
 
 Sometimes it can be useful to define powers that require context. To do so, just take an argument in your `power` block:
@@ -294,7 +276,6 @@ note = ...
 Power.current.client_note?(client, note)
 ```
 
-
 ### Optimizing record checks for scope powers
 
 You can query a scope power for a given record, e.g.
@@ -337,9 +318,7 @@ end
 
 This way you do not need to touch the database at all.
 
-
-Role-based permissions
-----------------------
+## Role-based permissions
 
 Consul has no built-in support for role-based permissions, but you can easily implement it yourself. Let's say your `User` model has a string column `role` which can be `"author"` or `"admin"`:
 
@@ -367,9 +346,7 @@ class Power
 end
 ```
 
-
-Controller integration
-----------------------
+## Controller integration
 
 It is convenient to expose the power for the current request to the rest of the application. Consul will help you with that if you tell it how to instantiate a power for the current request:
 
@@ -398,7 +375,6 @@ class NotesController < ApplicationController
 end
 ```
 
-
 ### Protect entry into controller actions
 
 To make sure a power is given before every action in a controller:
@@ -409,7 +385,7 @@ class NotesController < ApplicationController
 end
 ```
 
-You can use `:except` and `:only` options like in before\_actions.
+You can use `:except` and `:only` options like in before_actions.
 
 You can also map different powers to different actions:
 
@@ -441,7 +417,6 @@ class NotesController < ApplicationController
 end
 ```
 
-
 And if your power [requires context](#powers-that-require-context-arguments) (is parametrized), you can give it using the `:context` method:
 
 ```rb
@@ -458,8 +433,6 @@ class ClientNotesController < ApplicationController
 end
 ```
 
-
-
 ### Auto-mapping a power scope to a controller method
 
 It is often convenient to map a power scope to a private controller method:
@@ -486,7 +459,7 @@ class NotesController < ApplicationController
   power :notes, :as => :note_scope
 
   # ...
-    
+
   def note_scope
     super.where(trashed: false)
   end
@@ -494,7 +467,6 @@ class NotesController < ApplicationController
 end
 ```
 
-
 ### Multiple power-mappings for nested resources
 
 When using [nested resources](http://guides.rubyonrails.org/routing.html#nested-resources) you probably want two power
@@ -564,7 +536,7 @@ class ApplicationController < ActionController::Base
 end
 ```
 
-Note that this check is satisfied by *any* `.power` directive in the controller class or its ancestors, even if that `.power` directive has `:only` or `:except` options that do not apply to the current action.
+Note that this check is satisfied by _any_ `.power` directive in the controller class or its ancestors, even if that `.power` directive has `:only` or `:except` options that do not apply to the current action.
 
 Should you want to forego the power check (e.g. to remove authorization checks from an entirely public controller):
 
@@ -574,9 +546,7 @@ class ApiController < ApplicationController
 end
 ```
 
-
-Validating assignable values
-----------------------------
+## Validating assignable values
 
 Sometimes a scope is not enough to express what a user can edit. You will often want to give a user write access to a record, but restrict the values she can assign to a given field.
 
@@ -647,8 +617,7 @@ The `authorize_values_for` macro comes with many useful options and details best
 assignable_values_for :field, :through => lambda { Power.current }
 ```
 
-Memoization
------------
+## Memoization
 
 All power methods are [memoized](https://www.justinweiss.com/articles/4-simple-memoization-patterns-in-ruby-and-one-gem/) for performance reasons. Multiple calls to the same method will only call your block the first time, and return a cached result afterwards:
 
@@ -665,9 +634,7 @@ If you want to discard all cached results, call `#unmemoize_all`:
 power.unmemoize_all
 ```
 
-
-Dynamic power access
---------------------
+## Dynamic power access
 
 Consul gives you a way to dynamically access and query powers for a given name, model class or record.
 A common use case for this are generic helper methods, e.g. a method to display an "edit" link for any given record
@@ -687,30 +654,27 @@ end
 
 You can find a full list of available dynamic calls below:
 
-| Dynamic call                                            | Equivalent                                 |
-|---------------------------------------------------------|--------------------------------------------|
-| `Power.current.send(:notes)`                            | `Power.current.notes`                      |
-| `Power.current.include_power?(:notes)`                  | `Power.current.notes?`                     |
-| `Power.current.include_power!(:notes)`                  | `Power.current.notes!`                     |
-| `Power.current.include_object?(:notes, Note.last)`      | `Power.current.note?(Note.last)`           |
-| `Power.current.include_object!(:notes, Note.last)`      | `Power.current.note!(Note.last)`           |
-| `Power.current.for_model(Note)`                         | `Power.current.notes`                      |
-| `Power.current.for_model(:updatable, Note)`             | `Power.current.updatable_notes`            |
-| `Power.current.include_model?(Note)`                    | `Power.current.notes?`                     |
-| `Power.current.include_model?(:updatable, Note)`        | `Power.current.updatable_notes?`           |
-| `Power.current.include_model!(Note)`                    | `Power.current.notes!`                     |
-| `Power.current.include_model!(:updatable, Note)`        | `Power.current.updatable_notes!`           |
-| `Power.current.include_record?(Note.last)`              | `Power.current.note?(Note.last)`           |
-| `Power.current.include_record?(:updatable, Note.last)`  | `Power.current.updatable_note?(Note.last)` |
-| `Power.current.include_record!(Note.last)`              | `Power.current.note!(Note.last)`           |
-| `Power.current.include_record!(:updatable, Note.last)`  | `Power.current.updatable_note!(Note.last)` |
-| `Power.current.name_for_model(Note)`                    | `:notes`                                   |
-| `Power.current.name_for_model(:updatable, Note)`        | `:updatable_notes`                         |
-
-
-
-Querying a power that might be nil
-----------------------------------
+| Dynamic call                                           | Equivalent                                 |
+| ------------------------------------------------------ | ------------------------------------------ |
+| `Power.current.send(:notes)`                           | `Power.current.notes`                      |
+| `Power.current.include_power?(:notes)`                 | `Power.current.notes?`                     |
+| `Power.current.include_power!(:notes)`                 | `Power.current.notes!`                     |
+| `Power.current.include_object?(:notes, Note.last)`     | `Power.current.note?(Note.last)`           |
+| `Power.current.include_object!(:notes, Note.last)`     | `Power.current.note!(Note.last)`           |
+| `Power.current.for_model(Note)`                        | `Power.current.notes`                      |
+| `Power.current.for_model(:updatable, Note)`            | `Power.current.updatable_notes`            |
+| `Power.current.include_model?(Note)`                   | `Power.current.notes?`                     |
+| `Power.current.include_model?(:updatable, Note)`       | `Power.current.updatable_notes?`           |
+| `Power.current.include_model!(Note)`                   | `Power.current.notes!`                     |
+| `Power.current.include_model!(:updatable, Note)`       | `Power.current.updatable_notes!`           |
+| `Power.current.include_record?(Note.last)`             | `Power.current.note?(Note.last)`           |
+| `Power.current.include_record?(:updatable, Note.last)` | `Power.current.updatable_note?(Note.last)` |
+| `Power.current.include_record!(Note.last)`             | `Power.current.note!(Note.last)`           |
+| `Power.current.include_record!(:updatable, Note.last)` | `Power.current.updatable_note!(Note.last)` |
+| `Power.current.name_for_model(Note)`                   | `:notes`                                   |
+| `Power.current.name_for_model(:updatable, Note)`       | `:updatable_notes`                         |
+
+## Querying a power that might be nil
 
 You will often want to access `Power.current` from another model, to e.g. iterate through the list of accessible users:
 
@@ -760,23 +724,20 @@ end
 
 There is a long selection of class methods that behave neutrally in case `Power.current` is `nil`:
 
-| Call                                                     | Equivalent                                                          |
-|----------------------------------------------------------|---------------------------------------------------------------------|
-| `Power.for_model(Note)`                                  | `Power.current.present? ? Power.current.notes : Note`               |
-| `Power.for_model(:updatable, Note)`                      | `Power.current.present? ? Power.current.updatable_notes : Note`     |
-| `Power.include_model?(Note)`                             | `Power.current.present? ? Power.notes? : true`                      |
-| `Power.include_model?(:updatable, Note)`                 | `Power.current.present? ? Power.updatable_notes? : true`            |
-| `Power.include_model!(Note)`                             | `Power.notes! if Power.current.present?`                            |
-| `Power.include_model!(:updatable, Note)`                 | `Power.updatable_notes! if Power.current.present?`                  |
-| `Power.include_record?(Note.last)`                       | `Power.current.present? ? Power.note?(Note.last) : true`            |
-| `Power.include_record?(:updatable, Note.last)`           | `Power.current.present? ? Power.updatable_note?(Note.last?) : true` |
-| `Power.include_record!(Note.last)`                       | `Power.note!(Note.last) if Power.current.present?`                  |
-| `Power.include_record!(:updatable, Note.last)`           | `Power.updatable_note!(Note.last) if Power.current.present?`        |
-
-
-
-Testing
--------
+| Call                                           | Equivalent                                                          |
+| ---------------------------------------------- | ------------------------------------------------------------------- |
+| `Power.for_model(Note)`                        | `Power.current.present? ? Power.current.notes : Note`               |
+| `Power.for_model(:updatable, Note)`            | `Power.current.present? ? Power.current.updatable_notes : Note`     |
+| `Power.include_model?(Note)`                   | `Power.current.present? ? Power.notes? : true`                      |
+| `Power.include_model?(:updatable, Note)`       | `Power.current.present? ? Power.updatable_notes? : true`            |
+| `Power.include_model!(Note)`                   | `Power.notes! if Power.current.present?`                            |
+| `Power.include_model!(:updatable, Note)`       | `Power.updatable_notes! if Power.current.present?`                  |
+| `Power.include_record?(Note.last)`             | `Power.current.present? ? Power.note?(Note.last) : true`            |
+| `Power.include_record?(:updatable, Note.last)` | `Power.current.present? ? Power.updatable_note?(Note.last?) : true` |
+| `Power.include_record!(Note.last)`             | `Power.note!(Note.last) if Power.current.present?`                  |
+| `Power.include_record!(:updatable, Note.last)` | `Power.updatable_note!(Note.last) if Power.current.present?`        |
+
+## Testing
 
 This section Some hints for testing authorization with Consul.
 
@@ -847,9 +808,7 @@ Power.without_power do
 end
 ```
 
-
-Installation
-------------
+## Installation
 
 Add the following to your `Gemfile`:
 
@@ -859,9 +818,7 @@ gem 'consul'
 
 Now run `bundle install` to lock the gem into your project.
 
-
-Development
------------
+## Development
 
 We currently develop using Ruby 2.5.3 (see `.ruby-version`) since that version works for current versions of ActiveRecord that we support. GitHub Actions will test additional Ruby versions (2.3.8, 2.4.5, and 3.0.1).
 
@@ -884,8 +841,6 @@ Note that we have configured GitHub Actions to automatically run tests in all su
 
 I'm very eager to keep this gem leightweight and on topic. If you're unsure whether a change would make it into the gem, [talk to me beforehand](mailto:henning.koch@makandra.de).
 
-
-Credits
--------
+## Credits
 
 Henning Koch from [makandra](http://makandra.com/)

data/lib/consul/active_record.rb

@@ -14,4 +14,6 @@ module Consul
   end
 end
 
-ActiveRecord::Base.send(:extend, Consul::ActiveRecord)
+ActiveSupport.on_load(:active_record) do
+  extend(Consul::ActiveRecord)
+end

data/lib/consul/version.rb

@@ -1,3 +1,3 @@
 module Consul
-  VERSION = '1.3.1'
+  VERSION = '1.3.2'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: consul
 version: !ruby/object:Gem::Version
-  version: 1.3.1
+  version: 1.3.2
 platform: ruby
 authors:
 - Henning Koch
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-02-28 00:00:00.000000000 Z
+date: 2024-08-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: memoized
@@ -97,6 +97,8 @@ files:
 - Gemfile.6-1.lock
 - Gemfile.7-0
 - Gemfile.7-0.lock
+- Gemfile.7-1
+- Gemfile.7-1.lock
 - Gemfile.lock
 - LICENSE
 - README.md
@@ -135,7 +137,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.1
+rubygems_version: 3.5.11
 signing_key: 
 specification_version: 4
 summary: A scope-based authorization solution for Ruby on Rails.