ledermann-rails-settings 1.2.0 → 2.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7aa1af77c8b2aba3819e77ba00790f313f143e69
+  data.tar.gz: c4d85b477105c7f86dae04d5fb5b9245506fd1a2
+SHA512:
+  metadata.gz: 883960f19b067da03bc8f54d3de59d82d8640eeeb44d31b5ada5949a552a43027f59bec7b3854e9f9bc341c10126deb3c1714c0a6b6d4a5433639a9a1f53ebdb
+  data.tar.gz: 9786e48162d45e3a07020d268dc8dd9cbab7a2d5dd2bcc290a5ac47121f27bd4d0601fe75054d009773a95bf644390546aeaaf8b8425f5735a7eb06c02cdc2cb

data/.travis.yml

@@ -2,8 +2,7 @@ language: ruby
 rvm:
   - 1.8.7
   - 1.9.3
+  - 2.0.0
 gemfile:
-  - ci/Gemfile.rails-2.3.x
-#  - ci/Gemfile.rails-3.0.x
   - ci/Gemfile.rails-3.1.x
-  - ci/Gemfile.rails-3.2.x
+  - ci/Gemfile.rails-3.2.x

data/Changelog.md

@@ -1,17 +1,38 @@
+Version 2.0.0 (2013-03-07)
+
+- 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
+
+
+Version 1.2.1 (2013-02-09)
+
+- 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
+
+
 Version 1.2.0 (2012-07-21)
 
 - Added model-level settings (thanks to Jim Ryan)
 
+
 Version 1.1.0 (2012-06-01)
 
 - Added caching (thanks to Matthew McEachen)
 
+
 Version 1.0.1 (2011-11-05)
 
 - Gemspec: Fixed missing dependency
 
+
 Version 1.0.0 (2011-11-05)
 
 - Conversion from Plugin to Gem
 - Destroying false values (thanks to @Pavling)
-- Testing with Travis
+- Testing with Travis

data/Gemfile

@@ -1,4 +1,4 @@
-source "http://rubygems.org"
+source 'https://rubygems.org'
 
 # Specify your gem's dependencies in rails-settings.gemspec
 gemspec

data/MIT-LICENSE

@@ -1,5 +1,6 @@
-Copyright (c) 2006 Alex Wayne
-Some additional features added 2009-2012 by Georg Ledermann
+Copyright (c) 2013 Georg Ledermann
+
+MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
@@ -14,8 +15,8 @@ included in all copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOa AND
-NONINFRINGEMENT. IN NO EVENT SaALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
 LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,158 +1,133 @@
-# Settings Gem/Plugin for Rails
-
-[![Build Status](https://secure.travis-ci.org/ledermann/rails-settings.png)](http://travis-ci.org/ledermann/rails-settings)
-
-Settings is a gem/plugin that makes managing a table of key/value pairs easy. Think of it like a Hash stored in you database, that uses simple ActiveRecord like methods for manipulation. Keep track of any setting that you don't want to hard code into your rails app. You can store any kind of object: Strings, numbers, arrays, or any object which can be noted as YAML.
-
-
-## Requirements
-
-Rails 2.3.x, 3.1.x or 3.2.x (due to an [issue with Rails caching](https://github.com/rails/rails/pull/2010) it does not work properly with Rails 3.0.x)
-
-Tested with Ruby 1.8.7 and 1.9.3
-
-
-## Installation
-
-Include the gem in your Gemfile
-
-    gem 'ledermann-rails-settings', :require => 'rails-settings'
-
-or install as a plugin:
-
-    ./script/plugin install git://github.com/ledermann/rails-settings.git
-
-
-You have to create the table used by the Settings model by using this migration:
-
-    class CreateSettingsTable < ActiveRecord::Migration
-      def self.up
-        create_table :settings, :force => true do |t|
-          t.string  :var,         :null => false
-          t.text    :value
-          t.integer :target_id
-          t.string  :target_type, :limit => 30
-          t.timestamps
-        end
-
-        add_index :settings, [ :target_type, :target_id, :var ], :unique => true
-      end
-
-      def self.down
-        drop_table :settings
-      end
-    end
-    
-Now update your database with:
-
-    rake db:migrate
-
-## Usage
-
-The syntax is easy. First, lets create some settings to keep track of:
-
-    Settings.admin_password = 'supersecret'
-    Settings.date_format    = '%m %d, %Y'
-    Settings.cocktails      = ['Martini', 'Screwdriver', 'White Russian']
-    Settings.foo            = 123
-    Settings.credentials    = { :username => 'tom', :password => 'secret' }
-
-Now lets read them back:
-
-    Settings.foo
-    # => 123
-
-Changing an existing setting is the same as creating a new setting:
-
-    Settings.foo = 'super duper bar'
-
-For changing an existing setting which is a Hash, you can merge new values with existing ones:
-
-    Settings.merge! :credentials, :password => 'topsecret'
-    Settings.credentials
-    # => { :username => 'tom', :password => 'topsecret' }
-
-Decide you dont want to track a particular setting anymore?
-
-    Settings.destroy :foo
-    Settings.foo
-    # => nil
-
-Want a list of all the settings (including defaults)?
-
-    Settings.all
-    # => { 'admin_password' => 'super_secret', 'date_format' => '%m %d, %Y' }
-
-You need name spaces and want a list of settings for a give name space? Just choose your prefered named space delimiter and use Settings.all like this:
-
-    Settings['preferences.color'] = :blue
-    Settings['preferences.size'] = :large
-    Settings['license.key'] = 'ABC-DEF'
-    Settings.all('preferences.')
-    # => { 'preferences.color' => :blue, 'preferences.size' => :large }
-
-Settings may be bound to any existing ActiveRecord object. Define this association like this:
-
-    class User < ActiveRecord::Base
-      has_settings
-    end
-
-Then you can set/get a setting for a given user instance just by doing this:
-
-    user = User.find(123)
-    user.settings.color = :red
-    user.settings.color
-    # => :red
-    
-    user.settings.all
-    # => { "color" => :red }
-
-
-Set defaults for certain settings of your app.  This will cause the defined settings to return with the
-specified value even if they are not in the database.  Make a new file in config/initializers/settings.rb
-with the following:
-
-    Settings.defaults[:foo] = 'footastic'
-  
-Now even if the database is completely empty, you app will have some intelligent defaults:
-
-    Settings.foo
-    # => 'footastic'
-
-Defaults can be defined on the model level, too:
-
-    User.settings.foo = 'bar'
-    User.find(123).settings.foo
-    # => 'bar'
-
-If the setting doesn't exist on the object or the model, you'll get the default, as expected:
-
-    Settings.defaults[:some_default] = 'foo'
-    
-    User.settings.some_default
-    # => 'foo'
-    
-    User.find(123).settings.some_default
-    # => 'foo'
-
-
-I you want to find users having or not having some settings, there are named scopes for this:
-
-    User.with_settings
-    # returns a scope of users having any setting
-    
-    User.with_settings_for('color')
-    # returns a scope of users having a 'color' setting
-  
-    User.without_settings
-    # returns a scope of users having no setting at all (means user.settings.all == {})
-    
-    User.without_settings('color')
-    # returns a scope of users having no 'color' setting (means user.settings.color == nil)
-
-For better performance, you can enable caching, e.g.:
-
-    Settings.cache = ActiveSupport::Cache::MemoryStore.new
-    Settings.cache_options = { :expires_in => 5.minutes }
-
-That's all there is to it! Enjoy!
+# Settings for Rails 3
+
+[![Build Status](https://secure.travis-ci.org/ledermann/rails-settings.png)](http://travis-ci.org/ledermann/rails-settings)
+[![Code Climate](https://codeclimate.com/github/ledermann/rails-settings.png)](https://codeclimate.com/github/ledermann/rails-settings)
+
+Ruby gem to handle settings for ActiveRecord objects by storing them as serialized Hash in a separate database table. Optional: Defaults and Namespaces.
+
+**BEWARE: This is version 2 which is a complete rewrite and NOT compatible with version 1.x**
+
+
+## Example
+
+### Defining settings
+
+```ruby
+class User < ActiveRecord::Base
+  has_settings do |s|
+    s.key :dashboard, :defaults => { :theme => 'blue', :view => 'monthly', :filter => false }
+    s.key :calendar,  :defaults => { :scope => 'company'}
+  end
+end
+```
+
+If no defaults are needed, a simplified syntax can be used:
+
+```ruby
+class User < ActiveRecord::Base
+  has_settings :dashboard, :calendar
+end
+```
+
+Every setting is handled by the class `RailsSettings::SettingObject`. You can use your own class, e.g. for validations:
+
+```ruby
+class Project < ActiveRecord::Base
+  has_settings :info, :class_name => 'ProjectSettingObject'
+end
+
+class ProjectSettingObject < RailsSettings::SettingObject
+  validate do
+    unless self.owner_name.present? && self.owner_name.is_a?(String)
+      errors.add(:base, "Owner name is missing")
+    end
+  end
+end
+```
+
+### Set settings
+
+```ruby
+user = User.find(1)
+user.settings(:dashboard).theme = 'black'
+user.settings(:calendar).scope = 'all'
+user.settings(:calendar).display = 'daily'
+user.save! # saves new or changed settings, too
+```
+
+or
+
+```ruby
+user = User.find(1)
+user.settings(:dashboard).update_attributes! :theme => 'black'
+user.settings(:calendar).update_attributes! :scope => 'all', :display => 'dialy'
+```
+
+
+### Get settings
+
+```ruby
+user = User.find(1)
+user.settings(:dashboard).theme
+# => 'black
+
+user.settings(:dashboard).view
+# => 'monthly'  (it's the default)
+
+user.settings(:calendar).scope
+# => 'all'
+```
+
+
+### Using scopes
+
+```ruby
+User.with_settings
+# => all users having any setting
+
+User.without_settings
+# => all users without having any setting
+
+User.with_settings_for(:calendar)
+# => all users having a setting for 'calender'
+
+User.without_settings_for(:calendar)
+# => all users without having settings for 'calendar'
+```
+
+
+## Requirements
+
+Rails 3.1.x or 3.2.x
+Ruby 1.8.7, 1.9.3 or 2.0.0
+
+
+## Installation
+
+Include the gem in your Gemfile:
+
+```ruby
+gem 'ledermann-rails-settings', :require => 'rails-settings'
+```
+
+Generate and run the migration:
+
+```shell
+rails g rails_settings:migration
+rake db:migrate
+```
+
+## Compatibility
+
+Version 2 is a complete rewrite and has a new DSL, so it's **not** compatible with Version 1. But the database schema is unchanged, so you can use the same data after upgrading.
+In addition, Rails 2.3 is not supported anymore.
+
+If you don't want to upgrade, you find the old version in the [1.x](https://github.com/ledermann/rails-settings/commits/1.x) branch. But don't expect any updates there.
+
+
+## License
+
+MIT License
+Copyright (c) 2013 Georg Ledermann
+
+This gem is a complete rewrite of [rails-settings](https://github.com/Squeegy/rails-settings) by [Alex Wayne](https://github.com/Squeegy)

data/Rakefile

@@ -1,11 +1,6 @@
-require 'rake/testtask'
-
-Rake::TestTask.new do |t|
-  t.libs << 'lib' << 'test'
-  t.test_files = Dir.glob("test/**/*_test.rb")
-  t.verbose = true
-end
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
 
-task :default => :test
+RSpec::Core::RakeTask.new(:spec)
 
-require 'bundler/gem_tasks'
+task :default => :spec

data/ci/Gemfile.rails-3.1.x

@@ -1,5 +1,6 @@
 source :rubygems
 
-gem 'activerecord', '~> 3.1.4'
-gem 'sqlite3'
-gem 'rake'
+gem 'activerecord', '~> 3.1.0'
+gem 'sqlite3', '~> 1.3'
+gem 'rake', '~> 10.0'
+gem 'rspec', '~> 2.13'

data/ci/Gemfile.rails-3.2.x

@@ -1,5 +1,6 @@
 source :rubygems
 
-gem 'activerecord', '~> 3.2.2'
-gem 'sqlite3'
-gem 'rake'
+gem 'activerecord', '~> 3.2.0'
+gem 'sqlite3', '~> 1.3'
+gem 'rake', '~> 10.0'
+gem 'rspec', '~> 2.13'

data/lib/generators/rails_settings/migration/migration_generator.rb

@@ -0,0 +1,23 @@
+require 'rails/generators'
+require 'rails/generators/migration'
+
+module RailsSettings
+  class MigrationGenerator < Rails::Generators::Base
+    include Rails::Generators::Migration
+
+    desc "Generates migration for rails-settings"
+    source_root File.expand_path('../templates', __FILE__)
+
+    def create_migration_file
+      migration_template 'migration.rb', 'db/migrate/rails_settings_migration'
+    end
+
+    def self.next_migration_number(dirname)
+      if ActiveRecord::Base.timestamped_migrations
+        Time.now.utc.strftime("%Y%m%d%H%M%S")
+      else
+        "%.3d" % (current_migration_number(dirname) + 1)
+      end
+    end
+  end
+end

data/lib/generators/rails_settings/migration/templates/migration.rb

@@ -0,0 +1,15 @@
+class RailsSettingsMigration < ActiveRecord::Migration
+  def self.up
+    create_table :settings do |t|
+      t.string     :var,    :null => false
+      t.text       :value,  :null => false
+      t.references :target, :null => false, :polymorphic => true
+      t.timestamps
+    end
+    add_index :settings, [ :target_type, :target_id, :var ], :unique => true
+  end
+
+  def self.down
+    drop_table :settings
+  end
+end