bstard 0.2.3 → 0.2.4

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    MjRmN2FjOTNjZjJkOWI0NDcxMzU3MTNjZDkxMmM0MGQyMTliZTc1ZQ==
+    YjUzNDM2MWNmNTA1MjM5MTE5MDJhYTdlNjU2NWVhYTNmMWY0MGI5ZQ==
   data.tar.gz: !binary |-
-    NTNhZjk0MDJjNDk2YjE5ZGNjZmE3MTdmMGVkZmU0Zjg3NDk2NTE0Zg==
+    ZmE2MGQwY2M1YTVmYzJkMTAwY2ZhNWM3ZmUyYzVjMzNmODNhYmJhZg==
 SHA512:
   metadata.gz: !binary |-
-    NDY4MzExMjVhMTBiYjM4Nzc5MzY2YzUxODMwY2E0NTcxMTA4NjJkNDg5YWU3
-    MTdjNmY5NTMzYzg4NmU4MDUyYWVmZmM0ZWNjZTVlYWUyNTgxMDlmMzEwM2Zj
-    NGY3YjdjYmUzZjIyMjVkZGFjNTJlZjRjNmY0MDljZDlkMWIxZDM=
+    ZDhiZDcxNGU4MDgyNTgxN2YxYTViOWEzYjkwZWU0YjBmNjI1YmFlYWZmMmI0
+    N2M1MWU0ZWVjYTE5MDQ5ZGI3ZjA5NzlhMTU1NjcwNjFmZmIyNDIzZDhmN2Rh
+    ZTQ5YmQ3ZDk2ZTU5MTBjZWI3YjE3MjFmMjE5N2M4ZTcxYjU3NTk=
   data.tar.gz: !binary |-
-    MGYyZjIzYWE3ODA0MDdiYmI4NzRhOTFhNmNiMTRkZDVkMmEwNzU3OGY3YmQx
-    Y2U5OTdlOTQ1Y2YzNmU1YmM5ZWNjNTRlNjM4ODhhOTk1YTRmNjExMWFiNWEx
-    ZDdjZDVhOGQ3OGQyZjljOTIwNTgzZGZhODJkNDg5ODUwM2Y0OWE=
+    NDZjODEwNTg1NGJkN2U1ZGE1MDAxOGUwODI2ZTJiMDc0MzY1MTVkNjgyYzIy
+    NWFmZjVlNGYwMWEyYThlZjVkMWRmNmMxMmI2Yzg0NmViYmZiOGVlNjBmZjM1
+    ZmUyMmIzNDkxNDVlMzEwYTU4YmVkODE5NDIzOWNjYmY4NDg1YWM=

data/README.md

@@ -44,7 +44,7 @@ This defines a state machine that:
 Pretty simple huh?
 
 ### Initial State
-Set the initial state of the machine with `initial`. If no initial state is set a default state `:uninitialized` is used.
+Set the initial state of the machine with `initial`. If no initial state is set a default state `:uninitialized` is used. As a safeguard `initial` will ignore `nil` or empty string values.
 
 ### Querying the State
 
@@ -79,6 +79,22 @@ Helper methods are dynamically generated to enable querying whether an event can
   #=> false
 ```
 
+### Defining Events
+
+Events are defined by supplying an event name followed by one or more state transition declarations. Each state transition declaration is just a hash key value pair.  The key represents the starting state and the value the ending state.
+
+``` ruby
+  machine = Bstard.define do |fsm|
+    fsm.initial :new
+    fsm.event :save, :new => :draft
+    fsm.event :approve, :draft => :approved
+    fsm.event :publish, :approved => :published
+    fsm.event :delete, :draft => :deleted, :approved => :deleted
+  end
+```
+
+I find the spear `=>` Hash syntax style works best for me in describing the intent of the definition.
+
 ### Triggering Events
 
 Trigger events by sending a message using the event name suffixed with an exclamation mark.

data/lib/bstard/fsm.rb

@@ -10,7 +10,7 @@ class Bstard::Fsm
   end
 
   def initial(state)
-    unless state.nil?
+    unless state.nil? || state.empty?
       @current_state = state.to_sym
       add_state(current_state)
     end

data/lib/bstard/version.rb

@@ -1,4 +1,4 @@
 module Bstard
-  VERSION = '0.2.3'
+  VERSION = '0.2.4'
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bstard
 version: !ruby/object:Gem::Version
-  version: 0.2.3
+  version: 0.2.4
 platform: ruby
 authors:
 - Tony Headford
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-09-09 00:00:00.000000000 Z
+date: 2015-09-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler