Closed no-reply closed 4 years ago
there's a related issue on the reform-rails
side, asking for a pin to v2.2.x; https://github.com/trailblazer/reform-rails/issues/81
What version of reform-rails do you use ?
the version installed with the procedure above is 0.1.7
. that looks like the version in use in my actual projects, as well.
gem 'reform', '~> 2.3.1'
gem 'reform-rails', '~> 0.2.0.rc2'
can you try with this combo ?
that seems to patch the immediate issue. i'll try running a full build with that configuration.
forcing use of a release candidate isn't a workable solution for my project, though.
we will release it shortly.
Removal of
Reform::Form::Errors
in v2.3.1 is a breaking change for existing downstream gems.Should the release be yanked until a backwards compatible version exists?
Steps to reproduce
bundle init
gem 'rails'
,gem 'reform'
,gem 'reform-rails'
bundle install
; ensure Reform 2.3.1 is installedbundle console
require 'reform/form/active_model/validations'
Expected behavior
There should be no errors; activemodel validation should load normally.
Actual behavior
See backtrace below.
System configuration
Reform version: 2.3.1
Full Backtrace of Exception (if any)