CHANGE_NOTES.md in simplestate-2.0.5 vs CHANGE_NOTES.md in simplestate-2.0.6
- old
+ new
@@ -1,16 +1,24 @@
-#### SimpleState version 2.0.4
+#### SimpleState version 2.0.6
+Remove some cruft from testing setup.
+Code grooming.
+
+
+#### SimpleState version 2.0.5
Up date README to reflect creation of the simplestate-demo app.
Add #keys convenience method to StateList instances.
+#### SimpleState version 2.0.4
+Minor changes to README.
+AddGemfile.lock to the git tracked documents.
+
#### SimpleState version 2.0.3
Move maintenance of list of states available to an instance of StateList. This instance is held by the state holder. Allows multiple state holders to each have their own list of available states. Removes the effective global state being maintained in the State class.
-
#### SimpleState version 2.0.0
Ruby version requirement has changed to: __>= 2.1.0__ . (Ruby 2.0.0 can be used with some minor modification: Default values must be provided for all keyword arguments.)
State:
States are represented as 'singleton' instances of their respective classes and are referenced by their symbolized names.
@@ -23,11 +31,10 @@
StateHistory:
This has been added to separate the responsibility for management of state history from StateHolder.
-
#### SimpleState version 1.0.0
A state holder tracks the history of state transitions in an array accessed via __#state_history__. The array size defaults to 5. The last item in the array will be the most recent previous state instance. The size may be set at holder creation in the opts hash (:hx\_size\_limit). The history size limit has a getter and a setter defined as well. (__#hx\_size\_limit=__ and __#hx\_size\_limit__).
```ruby
class Button < StateHolder
@@ -48,10 +55,9 @@
assert_equal On, @button.prior_state
end
```
Please note that the State instance method, __#previous\_state\_class__, has been removed in this release.
-
#### SimpleState version 0.3.0
The 0.3.0 version contained a serious code smell: A state was expected to know about the history of state transitions. However, a state should know only the states to which it may transition and it's holder to support triggering those transitions. Knowlege of the transition history belongs with the state holder, if it is tracked at all.