acts_as_singleton 0.0.1 → 0.0.2

data/History.txt

@@ -1,3 +1,10 @@
+=== 0.0.2 / 2009-04-13
+
+* 1 minor enhancement
+
+  * Update regular expression to allow for a needed method.
+
+
 === 0.0.1 / 2009-03-30
 
 * 1 major enhancement

data/README.txt

@@ -11,6 +11,8 @@ It just makes sense to store mutable, site-wide, admin-level settings in the
 database. Right? A key-value table may be more flexible, but maybe we don't
 want to be flexible!
 
+If you truly want that flexibility: http://github.com/stephencelis/kvc
+
 
 == FEATURES/PROBLEMS
 

data/Rakefile

@@ -7,6 +7,7 @@ require "acts_as_singleton"
 Hoe.new("acts_as_singleton", ActiveRecord::Singleton::VERSION) do |p|
   p.developer("Stephen Celis", "stephen@stephencelis.com")
   p.remote_rdoc_dir = ''
+  p.rubyforge_name = %q{actsassingleton}
 end
 
 require 'rake'
@@ -29,6 +30,6 @@ Rake::RDocTask.new(:rdoc) do |rdoc|
   rdoc.rdoc_dir = 'rdoc'
   rdoc.title    = 'acts_as_singleton'
   rdoc.options << '--line-numbers' << '--inline-source'
-  rdoc.rdoc_files.include('README')
+  rdoc.rdoc_files.include('README.txt')
   rdoc.rdoc_files.include('lib/**/*.rb')
 end

data/lib/acts_as_singleton.rb

@@ -17,11 +17,11 @@ module ActiveRecord
   # clash with the <tt>ActiveRecord::Singleton::PRIVATE</tt> pattern, or
   # define them after including the module.
   module Singleton
-    VERSION = "0.0.1"
+    VERSION = "0.0.2"
 
     # This pattern matches methods that should be made private because they
     # should not be used in singleton classes.
-    PRIVATE = /^all(?:oc.*)?$|alloc|create|find|firs|mini|max|new|d_sco|upd/
+    PRIVATE = /^all(?:oc.*)?$|alloc|create|find|firs|mini|max|new|d_sco|^upd/
 
     def self.included(model)
       model.class_eval do

data/test/acts_as_singleton_test.rb

@@ -65,4 +65,10 @@ class ActsAsSingletonTest < ActiveSupport::TestCase
     assert_no_match(/id: .+?,/, HomepageSettings.inspect)
     assert_no_match(/id: .+?,/, HomepageSettings.instance.inspect)
   end
+
+  test "should be mutable" do
+    assert_nothing_raised do
+      HomepageSettings.instance.update_attributes! :welcome_message => "OH HAI"
+    end
+  end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: acts_as_singleton
 version: !ruby/object:Gem::Version 
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors: 
 - Stephen Celis
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-04-01 00:00:00 -05:00
+date: 2009-04-13 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -20,9 +20,9 @@ dependencies:
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
-        version: 1.11.0
+        version: 1.12.1
     version: 
-description: A lightweight singleton library for your Active Record models.  It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible!
+description: "A lightweight singleton library for your Active Record models.  It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible!  If you truly want that flexibility: http://github.com/stephencelis/kvc"
 email: 
 - stephen@stephencelis.com
 executables: []
@@ -43,6 +43,8 @@ files:
 - test/acts_as_singleton_test.rb
 has_rdoc: true
 homepage: http://github.com/stephencelis/acts_as_singleton
+licenses: []
+
 post_install_message: 
 rdoc_options: 
 - --main
@@ -63,8 +65,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   version: 
 requirements: []
 
-rubyforge_project: acts_as_singleton
-rubygems_version: 1.3.1
+rubyforge_project: actsassingleton
+rubygems_version: 1.3.5
 signing_key: 
 specification_version: 2
 summary: A lightweight singleton library for your Active Record models