Releases: ledermann/rails-settings
Releases · ledermann/rails-settings
v2.2.0
- Added RailsSettings::Base#to_settings_hash (thanks to @mguymon)
v2.1.0
- Support for Rails 4
- Removed support for Ruby 1.8.7
v2.0.3
- Fixed bug with setting getter when settings are booleans and default is true (thanks to @mduong)
v2.0.2
-
Changed database schema to allow NULL for column value
to fix serialization bug with MySQL. Thanks to @steventen for pointing this out in issue #31.
Important: The migration generator of version 2.0.0 and 2.0.1 was broken. If you use MySQL it's required to update your database schema like this:
class FixSettings < ActiveRecord::Migration
def up
change_column :settings, :value, :text, :null => true
end
def down
change_column :settings, :value, :text, :null => false
end
end
v2.0.1
- Added mass assignment security by protecting all regular attributes
v2.0.0
- Complete rewrite
- New DSL (see README.md)
- No global defaults anymore. Defaults are defined per ActiveRecord class
- No more storing defaults in the database
- Rails >= 3.1 needed (Rails 2.3 not supported anymore)
- Threadsafe
- Switched to RSpec for testing
v1.2.1
- Quick and dirty fix for design flaw in target scope implementation (thanks to Yves-Eric Martin)
- Use Thread.current instead of cattr_accessor to be threadsafe
- Code cleanup
v1.2.0
- Added model-level settings (thanks to Jim Ryan)
v1.1.0
- Added caching (thanks to Matthew McEachen)
v1.0.1
- Gemspec: Fixed missing dependency