state_pattern 2.0.0 → 2.0.1

data/lib/state_pattern/active_record.rb

@@ -10,7 +10,7 @@ module StatePattern
         end
 
         #enable after_initialize callback
-        if Rails.version >= "3.0.0"
+        if ::ActiveRecord::VERSION::STRING >= "3.0.0"
           def self.after_initialize; end
         else
           def after_initialize; end

data/test/state_pattern/active_record/test_helper.rb

@@ -1,5 +1,4 @@
 require 'test_helper'
-require 'rails'
 require 'active_record'
 
 {
@@ -22,5 +21,4 @@ end
 
 ActiveRecord::Base.establish_connection :adapter => :nulldb, :schema => 'schema.rb'
 
-require 'rails/init'
 require 'state_pattern/active_record'

metadata

@@ -1,13 +1,8 @@
 --- !ruby/object:Gem::Specification 
 name: state_pattern
 version: !ruby/object:Gem::Version 
-  hash: 15
-  prerelease: false
-  segments: 
-  - 2
-  - 0
-  - 0
-  version: 2.0.0
+  prerelease: 
+  version: 2.0.1
 platform: ruby
 authors: 
 - Daniel Cadenas
@@ -15,8 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-10-09 00:00:00 -02:00
-default_executable: 
+date: 2010-10-09 00:00:00 Z
 dependencies: []
 
 description: 
@@ -25,14 +19,13 @@ executables: []
 
 extensions: []
 
-extra_rdoc_files: 
-- LICENSE
-- README.rdoc
+extra_rdoc_files: []
+
 files: 
 - .document
 - .gitignore
 - LICENSE
-- README.rdoc
+- README.md
 - Rakefile
 - rails/init.rb
 - ./lib/state_pattern/active_record.rb
@@ -114,7 +107,6 @@ files:
 - ./examples/rails_3_button_example/db/development.sqlite3
 - ./examples/rails_3_button_example/db/migrate/20101009052900_create_buttons.rb
 - ./examples/rails_3_button_example/db/schema.rb
-- ./examples/rails_3_button_example/db/test.sqlite3
 - ./examples/rails_3_button_example/Gemfile
 - ./examples/rails_3_button_example/Gemfile.lock
 - ./examples/rails_3_button_example/log/development.log
@@ -137,13 +129,12 @@ files:
 - ./test/state_pattern_test.rb
 - ./test/test_class_creation_helper.rb
 - ./test/test_helper.rb
-has_rdoc: true
 homepage: http://github.com/dcadenas/state_pattern
 licenses: []
 
 post_install_message: 
-rdoc_options: 
-- --charset=UTF-8
+rdoc_options: []
+
 require_paths: 
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement 
@@ -151,23 +142,17 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 3
-      segments: 
-      - 0
       version: "0"
 required_rubygems_version: !ruby/object:Gem::Requirement 
   none: false
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 3
-      segments: 
-      - 0
       version: "0"
 requirements: []
 
 rubyforge_project: statepattern
-rubygems_version: 1.3.7
+rubygems_version: 1.8.16
 signing_key: 
 specification_version: 3
 summary: A Ruby state pattern implementation
@@ -248,7 +233,6 @@ test_files:
 - ./examples/rails_3_button_example/db/development.sqlite3
 - ./examples/rails_3_button_example/db/migrate/20101009052900_create_buttons.rb
 - ./examples/rails_3_button_example/db/schema.rb
-- ./examples/rails_3_button_example/db/test.sqlite3
 - ./examples/rails_3_button_example/Gemfile
 - ./examples/rails_3_button_example/Gemfile.lock
 - ./examples/rails_3_button_example/log/development.log
@@ -271,3 +255,4 @@ test_files:
 - ./test/state_pattern_test.rb
 - ./test/test_class_creation_helper.rb
 - ./test/test_helper.rb
+has_rdoc: 

data/README.rdoc

@@ -1,264 +0,0 @@
-= state_pattern
-
-A Ruby state pattern implementation.
-
-This library intentionally follows the classic state pattern implementation (no mixins, classical delegation to simple state classes, etc.) believing that it increases flexibility (internal DSL constraints vs plain object oriented Ruby power), simplicity and clarity.
-
-The gem is ready for Rails active record integration (see below and the examples folder).
-
-== Usage and functionality summary
-
-* Define the set of states you want your stateful object to have by creating a class for each state and inheriting from +StatePattern:State+.
-* All public methods defined in this state classes, except +enter+ and +exit+ (see below), are then available to the stateful object and their behaviour will depend on the current state . 
-* If this automatic delegation to the current state public methods is not enough for your stateful object then you can just reopen the method and use super whenever you want to call the state implementation.
-* Inside each state instance you can access the stateable object through the +stateful+ method.
-* Inside each state instance you can access the previous state through the +previous_state+ method.
-* Define +enter+ or +exit+ methods to hook any behaviour you want to execute whenever the stateful object enters or exits the state.
-* An event is just a method that calls +transition_to+ at some point.
-* If you want guards for some event just use plain old ifs before your +transition_to+.
-* In the stateful object you must +set_initial_state+.
-
-== Examples
-
-So here's a simple example that mimics a traffic semaphore
-
-  require 'rubygems'
-  require 'state_pattern'
-
-  class Stop < StatePattern::State
-    def next
-      sleep 3
-      transition_to(Go)
-    end
-
-    def color
-      "Red"
-    end
-  end
-
-  class Go < StatePattern::State
-    def next
-      sleep 2
-      transition_to(Caution)
-    end
-
-    def color
-      "Green"
-    end
-  end
-
-  class Caution < StatePattern::State
-    def next
-      sleep 1
-      transition_to(Stop)
-    end
-
-    def color
-      "Amber"
-    end
-  end
-
-  class TrafficSemaphore
-    include StatePattern
-    set_initial_state Stop
-  end
-
-  semaphore = TrafficSemaphore.new
-
-  loop do
-    puts semaphore.color
-    semaphore.next
-  end
-
-Let's now use one nice example from the AASM documentation and translate it to state_pattern.
-
-  require 'rubygems'
-  require 'state_pattern'
-
-  class Dating < StatePattern::State
-    def get_intimate
-      transition_to(Intimate) if stateable.drunk?
-    end
-
-    def get_married
-      transition_to(Married) if stateable.willing_to_give_up_manhood?
-    end
-
-    def enter
-      stateable.make_happy
-    end
-
-    def exit
-      stateable.make_depressed
-    end
-  end
-
-  class Intimate < StatePattern::State
-    def get_married
-      transition_to(Married) if stateable.willing_to_give_up_manhood?
-    end
-
-    def enter
-      stateable.make_very_happy
-    end
-
-    def exit
-      stateable.never_speak_again
-    end
-  end
-
-  class Married < StatePattern::State
-    def enter
-      stateable.give_up_intimacy
-    end
-
-    def exit
-      stateable.buy_exotic_car_and_wear_a_combover
-    end
-  end
-
-  class Relationship
-    include StatePattern
-    set_initial_state Dating
-
-    def drunk?; @drunk; end
-    def willing_to_give_up_manhood?; @give_up_manhood; end
-    def make_happy; end
-    def make_depressed; end
-    def make_very_happy; end
-    def never_speak_again; end
-    def give_up_intimacy; end
-    def buy_exotic_car_and_wear_a_combover; end
-  end
-
-== Enter and exit hooks
-
-Inside your state classes, any code that you put inside the enter method will be executed when the state is instantiated.
-You can also use the exit hook which is triggered when a successful transition to another state takes place.
-
-== Overriding automatic delegation
-
-If the automatic delegation to the current state public methods is not enough for your stateful object then you can just reopen the method and use super whenever you want to call the state implementation.
-
-  class TrafficSemaphore
-    include StatePattern
-    set_initial_state Stop
-
-    def color
-      # some great code here
-      #this calls the current state implementation
-      super 
-      # more cool hacking here
-    end
-  end
-
-== Rails
-
-To use the state pattern in your Rails models you need to:
-
-* Add a state column for your model table of type string
-* Include StatePattern::ActiveRecord in your model file
-* Use the state pattern as you would do in a plain Ruby class as shown above
-
-Please see the examples folder for a Rails 3 example.
-
-=== Example
-
-Note this is not the best example to show as ideally this plugin should be used with lot of state dependent behaviour and this is not the case.
-Remember to put each class in its correct file following Rails naming conventions.
-
-  module BlogStates
-    class StateBase < StatePattern::State
-      def submit!
-      end
-
-      def publish!
-      end
-
-      def reject!
-        transition_to(Rejected)
-        stateable.save!
-      end
-
-      def verify!
-      end
-    end
-
-    class Published < StateBase
-    end
-
-    class Pending < StateBase
-      def publish!
-        transition_to(Published) if stateable.valid?
-        stateable.save!
-      end
-    end
-
-    class Unverified < StateBase
-      def submit!
-        if stateable.submitter.manager?
-          if stateable.profile_complete?
-            transition_to(Published)
-          else
-            transition_to(Pending)
-          end
-
-          stateable.save!
-        end
-      end
-
-      def verify!
-        transition_to(Pending)
-        stateable.save!
-      end
-    end
-
-    class Rejected < StateBase
-      def publish!
-        transition_to(Published) if stateable.valid?
-        stateable.save!
-      end
-
-      def enter
-        Notifier.notify_blog_owner(stateable)
-      end
-    end
-  end
-
-  class Blog < ActiveRecord::Base
-    include StatePattern::ActiveRecord
-    set_initial_state Unverified
-
-     .
-     .
-     .
-
-  end
-
-=== The state attribute
-
-By default StatePattern::ActiveRecord expects a column named 'state' in the model. If you prefer to use another attribute do:
-
-  set_state_attribute :state_column
-
-=== How do I decide? state_pattern or {AASM}[http://github.com/rubyist/aasm]?
-
-* Lot of state dependent behavior? Lot of conditional logic depending on the state? => state_pattern
-* Not much state dependent behavior? => AASM
-
-== Thanks
-
-* {Alvaro Gil}[http://github.com/zevarito] for being the first using this gem in a real Rails project.
-* {Nicolás Sanguinetti}[http://github.com/foca] for his great feedback.
-
-== Installation
-
-  sudo gem install state_pattern
-
-== Collaborate
-
-http://github.com/dcadenas/state_pattern
-
-== Copyright
-
-Copyright (c) 2009 Daniel Cadenas. See LICENSE for details.