All Versions
89
Latest Version
Avg Release Cycle
87 days
Latest Release
882 days ago
Changelog History
Page 2
Changelog History
Page 2
-
v4.0.1 Changes
May 26, 2021๐ Fixed
- ๐ Fix regression of filter name relaxing.
- [#495][] - Fix time filter ignoring time zones
-
v4.0.0 Changes
January 10, 2021๐ Changed
- โฌ๏ธ drop support for Ruby < 2.5, added support for Ruby 3.0
- โฌ๏ธ drop support for Rails < 5.0, added support for Rails 6.1
- ๐ [#398][] - Predicate methods have been removed. (how to upgrade)
- [#412][] - Filters will now treat blank string values as
nil
(exceptstring
andsymbol
). (how to upgrade) - 0๏ธโฃ [#392][] - Integer parsing now defaults the base to 10. (how to upgrade)
- The
inputs
method now returns anActiveInteraction::Input
instead of a hash. TheActiveInteraction::Input
class still responds to all hash methods. - The
object
andrecord
filters now only accept an instance of the correct class type or a subclass of the correct class. They no longer allow you to check for included modules. (how to upgrade) - The
interface
filter will now look for an ancestor of the value passed based on the name of the interface or the value passed in thefrom
option. - The
InvalidClassError
has been replaced byInvalidNameError
. - When introspecting an array filter, the inner filter is referenced by :'0' instead of the singularized version of the array filter name.
โ Added
- Implicit coercion of types are now supported in filters (e.g.
to_str
,to_int
, etc). - The
interface
andrecord
filters, when used as an inner filter for anarray
, will have theirfrom/class
option set to a singularized version of thearray
filter name.
โฌ๏ธ Upgrading
Predicate Methods
๐ We've removed the predicate methods that were automatically generated for each input. They would return true if an input was not
nil
. They can be manually replaced with that same check. -
v3.8.3 Changes
August 23, 2020๐ Fixed
- #486
valid?
returns true if block not called and error added in execute around callback.
- #486
-
v3.8.2 Changes
April 22, 2020๐ Fixed
- [#479][] Composed interactions that throw errors now show a complete backtrace instead of ending at the
run!
of the outermost interaction.
- [#479][] Composed interactions that throw errors now show a complete backtrace instead of ending at the
-
v3.8.1 Changes
April 04, 2020๐ Fixed
- The implementation for providing a failing interaction on
InvalidInteractionError
was a breaking API change. It now works without breaking the API.
- The implementation for providing a failing interaction on
-
v3.8.0 Changes
February 28, 2020 -
v3.7.1 Changes
March 20, 2019 -
v3.7.0 Changes
February 10, 2019 -
v3.6.2 Changes
August 21, 2018๐ Fixed
- #411 Cache the result of outcome validations. This also resolves duplicate callbacks on composed interactions.
-
v3.6.1 Changes
November 12, 2017๐ Fixed
- #429 Pass details on translated detailed errors.