forked from slagyr/statemachine
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGES
119 lines (82 loc) · 3.41 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
= Statemachine Changelog
== Version 2.1.0
* Do not perform transitions if context method returns false | by @zombor (https://github.com/slagyr/statemachine/pull/11)
== Version 2.0.1
* initialize ivars so that runtimes running with -d don't complain about uninitialized ivars (chuckremes)
* updated to use Bundler and Rspec 2 (ericmeyer)
== Version 1.1.0
DotGraph
* DotGraph generator was added to generate graphs of statemachines using Omnigraffle.
* Fixed bug in Java generator where Statenames where not formated correctly.
== Version 1.0.0
Generator
* Java generator was added. Statemachines defined in the Ruby DSL can generate Java code.
== Version 0.4.2
Simple Fixes
* Fixed respond_to? to handle the, what should be impossible, case when the state is nil
* Switch history members variable to store id rather than object.
== Version 0.4.1
Simple Fixes
* Fixed priority of default transitions, self defaults first, then superstate defaults.
== Version 0.4.0
Feature enhancements
* enabled nested superstate history
* TransitionMissingException's are raised when the statemachine can't respond to an event
* Statmachine overrides respond_to? to respond to valid events.
Behavior Fixes
* fixed default transition so that superstate transitions have priority over default
== Version 0.3.0
Feature enhancements
* added default transitions
* added default history for superstates
* the context method in the builder will set the context's statemachine variable if the context respond_to?(:statemachine=)
Behavior Fixes
* the entry action of the startstate is called when the statemachine starts or is reset.
* resetting the statemachine will reset the history state for each superstate.
== Version 0.2.2
Minor plugin update
* introduced before_event and after_event hooks for controllers
== Version 0.2.1
Rails Plugin.
* Rails plugin introduced
== Version 0.2.0
Separation of logic from behavior.
* Prefered builder syntax implemented
* statemachine have a context which defines all the behavior
* startstate can be set at any time in the builder
* states can be declared without blocks
* context can be set in builder
== Version 0.1.0
A new way to build the statemachines
* cleaner API for running a statemachine
* much refactoring
* new API for building statemachine
* process_event accepts strings
== Version 0.0.4
Some minor improvements
* Proper handling of state transition implemented, such that the proper state is set for entry and exit actions.
* can now use State objects in addition to symbols while creating a transition
* more compliant implementation of history state
== Version 0.0.3
Bug fix dealing with entry and exit actions. The state machine's state need to be set to the entered/exited state before calling the
exit/entry action.
* added a couple specs in the exit_entry_spec
* modified state.entered/exited methods to set the state
* modifed the StateMachine.state to accept state objects.
* removed running attribute from StateMachine because it wasn't much use
* also removed the nil (end state)
== Version 0.0.2
More conventional file structure
* nothing much to report in terms of changes.
== Version 0.0.1
0.0.0 didn't seem to work as a gem so maybe this one will.
* nothing really, just playing with rake and release configuration
== Version 0.0.0
The first release. Most finite state machine features are implemented
* states
* transitions
* transition actions
* super states
* entry actions
* exit actions
* history state