activemodel 7.0.8.7 → 7.1.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f65c2aa43d05d67e900b3b12ac60c411899082b9a0570f86cac06af8f4375abd
-  data.tar.gz: d0b726b2429632680b2c9d12cdcbf652b536c00e192b983a9c5ccd7da2fdae34
+  metadata.gz: 9f79873d7c2a9772e4c9ca33cf468880b923a818c11b874eb7c8c40954a1e652
+  data.tar.gz: a264d11a6a4a6783d08513145436a78440847774f64ab8bfe5436e0e0c56224b
 SHA512:
-  metadata.gz: bbb5722f3e0928497062d7672d917d845127309decbc209415c4f8785a48d7ec2520441c5acc9ca6dea91a412d3b57423d3d6f88ea1e0903959c9fb108ab6307
-  data.tar.gz: cbebd0f6c2c12e2cfe7725654a1bd7c88894492aef219fce5c7b168e53ed008f430117cd2e9da2f0e8fd3e229501b6314d3e7320742a792dea5bfa46dd2a994c
+  metadata.gz: 7019a3654dabd54a630605e8b032450f170fe5aa8f3fa0ec626f80546dbf9c09cea143bed32356608319b059127ede72aae6e08c5a280dfae9021e98f027640f
+  data.tar.gz: 72936b14496e7b9465b6cdaf7894b80b502bb275e58f7e4b9e52d67ccfd671ee1a4f952ea3da25b504147d81a645755a4cb16dde63f4ecbc68b6787636201b0b

data/CHANGELOG.md

@@ -1,299 +1,306 @@
-## Rails 7.0.8.7 (December 10, 2024) ##
+## Rails 7.1.5.1 (December 10, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.8.6 (October 23, 2024) ##
-
-*   No changes.
-
-
-## Rails 7.0.8.5 (October 15, 2024) ##
-
-*   No changes.
+## Rails 7.1.5 (October 30, 2024) ##
 
+*   Fix regression in `alias_attribute` to work with user defined methods.
 
-## Rails 7.0.8.4 (June 04, 2024) ##
-
-*   No changes.
+    `alias_attribute` would wrongly assume the attribute accessor was generated by Active Model.
 
+    ```ruby
+    class Person
+      include ActiveModel::AttributeMethods
 
-## Rails 7.0.8.3 (May 17, 2024) ##
-
-*   No changes.
-
-
-## Rails 7.0.8.2 (May 16, 2024) ##
-
-*   No changes.
-
-
-## Rails 7.0.8.1 (February 21, 2024) ##
-
-*   No changes.
+      define_attribute_methods :name
+      attr_accessor :name
 
+      alias_attribute :full_name, :name
+    end
 
-## Rails 7.0.8 (September 09, 2023) ##
+    person.full_name # => NoMethodError: undefined method `attribute' for an instance of Person
+    ```
 
-*   No changes.
+    *Jean Boussier*
 
 
-## Rails 7.0.7.2 (August 22, 2023) ##
+## Rails 7.1.4.2 (October 23, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.7.1 (August 22, 2023) ##
+## Rails 7.1.4.1 (October 15, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.7 (August 09, 2023) ##
-
-*   Error.full_message now strips ":base" from the message.
-
-    *zzak*
-
-*   Add a load hook for `ActiveModel::Model` (named `active_model`) to match the load hook for
-    `ActiveRecord::Base` and allow for overriding aspects of the `ActiveModel::Model` class.
-
-
-## Rails 7.0.6 (June 29, 2023) ##
+## Rails 7.1.4 (August 22, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.5.1 (June 26, 2023) ##
+## Rails 7.1.3.4 (June 04, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.5 (May 24, 2023) ##
+## Rails 7.1.3.3 (May 16, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.4.3 (March 13, 2023) ##
+## Rails 7.1.3.2 (February 21, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.4.2 (January 24, 2023) ##
+## Rails 7.1.3.1 (February 21, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.4.1 (January 17, 2023) ##
+## Rails 7.1.3 (January 16, 2024) ##
 
 *   No changes.
 
 
-## Rails 7.0.4 (September 09, 2022) ##
+## Rails 7.1.2 (November 10, 2023) ##
 
-*   Handle name clashes in attribute methods code generation cache.
+*   Make `==(other)` method of AttributeSet safe.
 
-    When two distinct attribute methods would generate similar names,
-    the first implementation would be incorrectly re-used.
+    *Dmitry Pogrebnoy*
 
-    ```ruby
-    class A
-      attribute_method_suffix "_changed?"
-      define_attribute_methods :x
-    end
 
-    class B
-      attribute_method_suffix "?"
-      define_attribute_methods :x_changed
-    end
-    ```
-
-    *Jean Boussier*
-
-## Rails 7.0.3.1 (July 12, 2022) ##
+## Rails 7.1.1 (October 11, 2023) ##
 
 *   No changes.
 
 
-## Rails 7.0.3 (May 09, 2022) ##
+## Rails 7.1.0 (October 05, 2023) ##
 
 *   No changes.
 
 
-## Rails 7.0.2.4 (April 26, 2022) ##
+## Rails 7.1.0.rc2 (October 01, 2023) ##
 
 *   No changes.
 
 
-## Rails 7.0.2.3 (March 08, 2022) ##
-
-*   No changes.
+## Rails 7.1.0.rc1 (September 27, 2023) ##
 
+*   Remove change in the typography of user facing error messages.
+    For example, “can’t be blank” is again “can't be blank”.
 
-## Rails 7.0.2.2 (February 11, 2022) ##
-
-*   No changes.
-
+    *Rafael Mendonça França*
 
-## Rails 7.0.2.1 (February 11, 2022) ##
 
-*   No changes.
+## Rails 7.1.0.beta1 (September 13, 2023) ##
 
+*   Support composite identifiers in `to_key`
 
-## Rails 7.0.2 (February 08, 2022) ##
+    `to_key` avoids wrapping `#id` value into an `Array` if `#id` already an array
 
-*   Use different cache namespace for proxy calls
+    *Nikita Vasilevsky*
 
-    Models can currently have different attribute bodies for the same method
-    names, leading to conflicts. Adding a new namespace `:active_model_proxy`
-    fixes the issue.
+*   Add `ActiveModel::Conversion.param_delimiter` to configure delimiter being used in `to_param`
 
-    *Chris Salzberg*
+    *Nikita Vasilevsky*
 
+*   `undefine_attribute_methods` undefines alias attribute methods along with attribute methods.
 
-## Rails 7.0.1 (January 06, 2022) ##
+    *Nikita Vasilevsky*
 
-*   No changes.
+*   Error.full_message now strips ":base" from the message.
 
+    *zzak*
 
-## Rails 7.0.0 (December 15, 2021) ##
+*   Add a load hook for `ActiveModel::Model` (named `active_model`) to match the load hook for
+    `ActiveRecord::Base` and allow for overriding aspects of the `ActiveModel::Model` class.
 
-*   No changes.
+    *Lewis Buckley*
 
+*   Improve password length validation in ActiveModel::SecurePassword to consider byte size for BCrypt
+    compatibility.
 
-## Rails 7.0.0.rc3 (December 14, 2021) ##
+    The previous password length validation only considered the character count, which may not
+    accurately reflect the 72-byte size limit imposed by BCrypt. This change updates the validation
+    to consider both character count and byte size while keeping the character length validation in place.
 
-*   No changes.
+    ```ruby
+    user = User.new(password: "a" * 73)  # 73 characters
+    user.valid? # => false
+    user.errors[:password] # => ["is too long"]
 
 
-## Rails 7.0.0.rc2 (December 14, 2021) ##
+    user = User.new(password: "あ" * 25)  # 25 characters, 75 bytes
+    user.valid? # => false
+    user.errors[:password] # => ["is too long"]
+    ```
 
-*   No changes.
+    *ChatGPT*, *Guillermo Iguaran*
 
-## Rails 7.0.0.rc1 (December 06, 2021) ##
+*   `has_secure_password` now generates an `#{attribute}_salt` method that returns the salt
+    used to compute the password digest. The salt will change whenever the password is changed,
+    so it can be used to create single-use password reset tokens with `generates_token_for`:
 
-*   Remove support to Marshal load Rails 5.x `ActiveModel::AttributeSet` format.
+    ```ruby
+    class User < ActiveRecord::Base
+      has_secure_password
 
-    *Rafael Mendonça França*
+      generates_token_for :password_reset, expires_in: 15.minutes do
+        password_salt&.last(10)
+      end
+    end
+    ```
 
-*   Remove support to Marshal and YAML load Rails 5.x error format.
+    *Lázaro Nixon*
 
-    *Rafael Mendonça França*
+*   Improve typography of user facing error messages. In English contractions,
+    the Unicode APOSTROPHE (`U+0027`) is now RIGHT SINGLE QUOTATION MARK
+    (`U+2019`). For example, "can't be blank" is now "can’t be blank".
 
-*   Remove deprecated support to use `[]=` in `ActiveModel::Errors#messages`.
+    *Jon Dufresne*
 
-    *Rafael Mendonça França*
+*   Add class to `ActiveModel::MissingAttributeError` error message.
 
-*   Remove deprecated support to `delete` errors from `ActiveModel::Errors#messages`.
+    Show which class is missing the attribute in the error message:
 
-    *Rafael Mendonça França*
+    ```ruby
+    user = User.first
+    user.pets.select(:id).first.user_id
+    # => ActiveModel::MissingAttributeError: missing attribute 'user_id' for Pet
+    ```
 
-*   Remove deprecated support to `clear` errors from `ActiveModel::Errors#messages`.
+    *Petrik de Heus*
 
-    *Rafael Mendonça França*
+*   Raise `NoMethodError` in `ActiveModel::Type::Value#as_json` to avoid unpredictable
+    results.
 
-*   Remove deprecated support concat errors to `ActiveModel::Errors#messages`.
+    *Vasiliy Ermolovich*
 
-    *Rafael Mendonça França*
+*   Custom attribute types that inherit from Active Model built-in types and do
+    not override the `serialize` method will now benefit from an optimization
+    when serializing attribute values for the database.
 
-*   Remove deprecated `ActiveModel::Errors#to_xml`.
+    For example, with a custom type like the following:
 
-    *Rafael Mendonça França*
-
-*   Remove deprecated `ActiveModel::Errors#keys`.
+    ```ruby
+    class DowncasedString < ActiveModel::Type::String
+      def cast(value)
+        super&.downcase
+      end
+    end
 
-    *Rafael Mendonça França*
+    ActiveRecord::Type.register(:downcased_string, DowncasedString)
 
-*   Remove deprecated `ActiveModel::Errors#values`.
+    class User < ActiveRecord::Base
+      attribute :email, :downcased_string
+    end
 
-    *Rafael Mendonça França*
+    user = User.new(email: "FooBar@example.com")
+    ```
 
-*   Remove deprecated `ActiveModel::Errors#slice!`.
+    Serializing the `email` attribute for the database will be roughly twice as
+    fast.  More expensive `cast` operations will likely see greater improvements.
 
-    *Rafael Mendonça França*
+    *Jonathan Hefner*
 
-*   Remove deprecated `ActiveModel::Errors#to_h`.
+*   `has_secure_password` now supports password challenges via a
+    `password_challenge` accessor and validation.
 
-    *Rafael Mendonça França*
+    A password challenge is a safeguard to verify that the current user is
+    actually the password owner.  It can be used when changing sensitive model
+    fields, such as the password itself.  It is different than a password
+    confirmation, which is used to prevent password typos.
 
-*   Remove deprecated enumeration of `ActiveModel::Errors` instances as a Hash.
+    When `password_challenge` is set, the validation checks that the value's
+    digest matches the *currently persisted* `password_digest` (i.e.
+    `password_digest_was`).
 
-    *Rafael Mendonça França*
+    This allows a password challenge to be done as part of a typical `update`
+    call, just like a password confirmation.  It also allows a password
+    challenge error to be handled in the same way as other validation errors.
 
-*   Clear secure password cache if password is set to `nil`
+    For example, in the controller, instead of:
 
-    Before:
+    ```ruby
+    password_params = params.require(:password).permit(
+      :password_challenge,
+      :password,
+      :password_confirmation,
+    )
 
-       user.password = 'something'
-       user.password = nil
+    password_challenge = password_params.delete(:password_challenge)
+    @password_challenge_failed = !current_user.authenticate(password_challenge)
 
-       user.password # => 'something'
+    if !@password_challenge_failed && current_user.update(password_params)
+      # ...
+    end
+    ```
 
-    Now:
+    You can now write:
 
-       user.password = 'something'
-       user.password = nil
+    ```ruby
+    password_params = params.require(:password).permit(
+      :password_challenge,
+      :password,
+      :password_confirmation,
+    ).with_defaults(password_challenge: "")
+
+    if current_user.update(password_params)
+      # ...
+    end
+    ```
 
-       user.password # => nil
+    And, in the view, instead of checking `@password_challenge_failed`, you can
+    render an error for the `password_challenge` field just as you would for
+    other form fields, including utilizing `config.action_view.field_error_proc`.
 
-    *Markus Doits*
+    *Jonathan Hefner*
 
-## Rails 7.0.0.alpha2 (September 15, 2021) ##
+*   Support infinite ranges for `LengthValidator`s `:in`/`:within` options
 
-*   No changes.
+    ```ruby
+    validates_length_of :first_name, in: ..30
+    ```
 
+    *fatkodima*
 
-## Rails 7.0.0.alpha1 (September 15, 2021) ##
+*   Add support for beginless ranges to inclusivity/exclusivity validators:
 
-*   Introduce `ActiveModel::API`.
+    ```ruby
+    validates_inclusion_of :birth_date, in: -> { (..Date.today) }
+    ```
 
-    Make `ActiveModel::API` the minimum API to talk with Action Pack and Action View.
-    This will allow adding more functionality to `ActiveModel::Model`.
+    ```ruby
+    validates_exclusion_of :birth_date, in: -> { (..Date.today) }
+    ```
 
-    *Petrik de Heus*, *Nathaniel Watts*
+    *Bo Jeanes*
 
-*   Fix dirty check for Float::NaN and BigDecimal::NaN.
+*   Make validators accept lambdas without record argument
 
-    Float::NaN and BigDecimal::NaN in Ruby are [special values](https://bugs.ruby-lang.org/issues/1720)
-    and can't be compared with `==`.
+    ```ruby
+    # Before
+    validates_comparison_of :birth_date, less_than_or_equal_to: ->(_record) { Date.today }
 
-    *Marcelo Lauxen*
+    # After
+    validates_comparison_of :birth_date, less_than_or_equal_to: -> { Date.today }
+    ```
 
-*   Fix `to_json` for `ActiveModel::Dirty` object.
+    *fatkodima*
 
-    Exclude `mutations_from_database` attribute from json as it lead to recursion.
+*   Fix casting long strings to `Date`, `Time` or `DateTime`
 
-    *Anil Maurya*
+    *fatkodima*
 
-*   Add `ActiveModel::AttributeSet#values_for_database`.
+*   Use different cache namespace for proxy calls
 
-    Returns attributes with values for assignment to the database.
+    Models can currently have different attribute bodies for the same method
+    names, leading to conflicts. Adding a new namespace `:active_model_proxy`
+    fixes the issue.
 
     *Chris Salzberg*
 
-*   Fix delegation in ActiveModel::Type::Registry#lookup and ActiveModel::Type.lookup.
-
-    Passing a last positional argument `{}` would be incorrectly considered as keyword argument.
-
-    *Benoit Daloze*
-
-*   Cache and re-use generated attribute methods.
-
-    Generated methods with identical implementations will now share their instruction sequences
-    leading to reduced memory retention, and slightly faster load time.
-
-    *Jean Boussier*
-
-*   Add `in: range`  parameter to `numericality` validator.
-
-    *Michal Papis*
-
-*   Add `locale` argument to `ActiveModel::Name#initialize` to be used to generate the `singular`,
-   `plural`, `route_key` and `singular_route_key` values.
-
-    *Lukas Pokorny*
-
-*   Make ActiveModel::Errors#inspect slimmer for readability
-
-    *lulalala*
-
-Please check [6-1-stable](https://github.com/rails/rails/blob/6-1-stable/activemodel/CHANGELOG.md) for previous changes.
+Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/activemodel/CHANGELOG.md) for previous changes.

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2004-2022 David Heinemeier Hansson
+Copyright (c) David Heinemeier Hansson
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.rdoc

@@ -1,22 +1,22 @@
-= Active Model -- model interfaces for Rails
+= Active Model -- model interfaces for \Rails
 
 Active Model provides a known set of interfaces for usage in model classes.
 They allow for Action Pack helpers to interact with non-Active Record models,
 for example. Active Model also helps with building custom ORMs for use outside of
-the Rails framework.
+the \Rails framework.
 
-You can read more about Active Model in the {Active Model Basics}[https://edgeguides.rubyonrails.org/active_model_basics.html] guide.
+You can read more about Active Model in the {Active Model Basics}[https://guides.rubyonrails.org/active_model_basics.html] guide.
 
-Prior to Rails 3.0, if a plugin or gem developer wanted to have an object
+Prior to \Rails 3.0, if a plugin or gem developer wanted to have an object
 interact with Action Pack helpers, it was required to either copy chunks of
-code from Rails, or monkey patch entire helpers to make them handle objects
+code from \Rails, or monkey patch entire helpers to make them handle objects
 that did not exactly conform to the Active Record interface. This would result
 in code duplication and fragile applications that broke on upgrades. Active
 Model solves this by defining an explicit API. You can read more about the
-API in <tt>ActiveModel::Lint::Tests</tt>.
+API in +ActiveModel::Lint::Tests+.
 
 Active Model provides a default module that implements the basic API required
-to integrate with Action Pack out of the box: <tt>ActiveModel::API</tt>.
+to integrate with Action Pack out of the box: ActiveModel::API.
 
     class Person
       include ActiveModel::API
@@ -32,7 +32,7 @@ to integrate with Action Pack out of the box: <tt>ActiveModel::API</tt>.
 
 It includes model name introspections, conversions, translations and
 validations, resulting in a class suitable to be used with Action Pack.
-See <tt>ActiveModel::API</tt> for more examples.
+See ActiveModel::API for more examples.
 
 Active Model also provides the following functionality to have ORM-like
 behavior out of the box:
@@ -156,7 +156,7 @@ behavior out of the box:
 
 * Making objects serializable
 
-  <tt>ActiveModel::Serialization</tt> provides a standard interface for your object
+  ActiveModel::Serialization provides a standard interface for your object
   to provide +to_json+ serialization.
 
     class SerialPerson

data/lib/active_model/access.rb

@@ -0,0 +1,16 @@
+# frozen_string_literal: true
+
+require "active_support/core_ext/enumerable"
+require "active_support/core_ext/hash/indifferent_access"
+
+module ActiveModel
+  module Access # :nodoc:
+    def slice(*methods)
+      methods.flatten.index_with { |method| public_send(method) }.with_indifferent_access
+    end
+
+    def values_at(*methods)
+      methods.flatten.map! { |method| public_send(method) }
+    end
+  end
+end

data/lib/active_model/api.rb

@@ -1,10 +1,10 @@
 # frozen_string_literal: true
 
 module ActiveModel
-  # == Active \Model \API
+  # = Active \Model \API
   #
   # Includes the required interface for an object to interact with
-  # Action Pack and Action View, using different Active Model modules.
+  # Action Pack and Action View, using different Active \Model modules.
   # It includes model name introspections, conversions, translations, and
   # validations. Besides that, it allows you to initialize the object with a
   # hash of attributes, pretty much like Active Record does.
@@ -20,7 +20,7 @@ module ActiveModel
   #   person.name # => "bob"
   #   person.age  # => "18"
   #
-  # Note that, by default, <tt>ActiveModel::API</tt> implements <tt>persisted?</tt>
+  # Note that, by default, +ActiveModel::API+ implements #persisted?
   # to return +false+, which is the most common case. You may want to override
   # it in your class to simulate a different scenario:
   #
@@ -36,7 +36,7 @@ module ActiveModel
   #   person = Person.new(id: 1, name: 'bob')
   #   person.persisted? # => true
   #
-  # Also, if for some reason you need to run code on <tt>initialize</tt>, make
+  # Also, if for some reason you need to run code on initialize ( ::new ), make
   # sure you call +super+ if you want the attributes hash initialization to
   # happen.
   #
@@ -54,7 +54,7 @@ module ActiveModel
   #   person.omg # => true
   #
   # For more detailed information on other functionalities available, please
-  # refer to the specific modules included in <tt>ActiveModel::API</tt>
+  # refer to the specific modules included in +ActiveModel::API+
   # (see below).
   module API
     extend ActiveSupport::Concern

data/lib/active_model/attribute/user_provided_default.rb

@@ -4,6 +4,10 @@ require "active_model/attribute"
 
 module ActiveModel
   class Attribute # :nodoc:
+    def with_user_default(value)
+      UserProvidedDefault.new(name, value, type, self.is_a?(FromDatabase) ? self : original_attribute)
+    end
+
     class UserProvidedDefault < FromUser # :nodoc:
       def initialize(name, value, type, database_default)
         @user_provided_value = value

data/lib/active_model/attribute.rb

@@ -53,7 +53,10 @@ module ActiveModel
     end
 
     def value_for_database
-      type.serialize(value)
+      if !defined?(@value_for_database) || type.changed_in_place?(@value_for_database, value)
+        @value_for_database = _value_for_database
+      end
+      @value_for_database
     end
 
     def serializable?(&block)
@@ -159,6 +162,10 @@ module ActiveModel
         assigned? && type.changed?(original_value, value, value_before_type_cast)
       end
 
+      def _value_for_database
+        type.serialize(value)
+      end
+
       def _original_value_for_database
         type.serialize(original_value)
       end
@@ -168,6 +175,19 @@ module ActiveModel
           type.deserialize(value)
         end
 
+        def forgetting_assignment
+          # If this attribute was not persisted (with a `value_for_database`
+          # that might differ from `value_before_type_cast`) and `value` has not
+          # changed in place, we can use the existing `value_before_type_cast`
+          # to avoid deserialize / cast / serialize calls from computing the new
+          # attribute's `value_before_type_cast`.
+          if !defined?(@value_for_database) && !changed_in_place?
+            with_value_from_database(value_before_type_cast)
+          else
+            super
+          end
+        end
+
         private
           def _original_value_for_database
             value_before_type_cast
@@ -182,6 +202,11 @@ module ActiveModel
         def came_from_user?
           !type.value_constructed_by_mass_assignment?(value_before_type_cast)
         end
+
+        private
+          def _value_for_database
+            Type::SerializeCastValue.serialize(type, value)
+          end
       end
 
       class WithCastValue < Attribute # :nodoc: