diff options
author | Godfrey Chan <godfreykfc@gmail.com> | 2014-01-03 09:31:01 -0800 |
---|---|---|
committer | Godfrey Chan <godfreykfc@gmail.com> | 2014-01-03 09:31:01 -0800 |
commit | 788bb40e3887e2718f07be769b80818d653638f0 (patch) | |
tree | f66c4334fc261ed18955853ce3da796935a24a4f /railties/bin | |
parent | 97e7ca48c139ea5cce2fa9b4be631946252a1ebd (diff) | |
download | rails-788bb40e3887e2718f07be769b80818d653638f0.tar.gz rails-788bb40e3887e2718f07be769b80818d653638f0.tar.bz2 rails-788bb40e3887e2718f07be769b80818d653638f0.zip |
Building new records with enum scopes now works as expected
Previously, this would give an `ArgumentError`:
class Issue < ActiveRecord::Base
enum :status, [:open, :finished]
end
Issue.open.build # => ArgumentError: '0' is not a valid status
Issue.open.create # => ArgumentError: '0' is not a valid status
PR #13542 muted the error, but the issue remains. This commit fixes
the issue by allowing the enum value to be written directly via the
setter:
Issue.new.status = 0 # This now sets status to :open
Assigning a value directly via the setter like this is not part of the
documented public API, so users should not rely on this behavior.
Closes #13530.
Diffstat (limited to 'railties/bin')
0 files changed, 0 insertions, 0 deletions