kotovalexarian-likes-github
/
aasm
mirror of https://github.com/aasm/aasm
1
0
Fork 0
Code Releases Activity

Update README.md (#649) 

add further information re: column names when you have multiple state machines. I'm no expert, but please do confirm that we need to explicitly write in the column names when we have more than one state machine operating in a single model? Pls confirm.
This commit is contained in:
Ben Koshy 2019-09-25 00:12:46 +10:00 committed by Anil Kumar Maurya
parent 1f5bec7811
commit 31a3d83411
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -436,12 +436,12 @@ job.aasm.current_state # stage3
### Multiple state machines per class
Multiple state machines per class are supported. Be aware though that _AASM_ has been
built with one state machine per class in mind. Nonetheless, here's how to do it:
built with one state machine per class in mind. Nonetheless, here's how to do it (see below). Please note that you will need to specify database columns for where your pertinent states will be stored - we have specified two columns `move_state` and `work_state` in the example below. See the [Column name & migration](https://github.com/aasm/aasm#column-name--migration) section for further info.
```ruby
class SimpleMultipleExample
include AASM
aasm(:move) do
aasm(:move, column: 'move_state') do
state :standing, initial: true
state :walking
state :running
@ -457,7 +457,7 @@ class SimpleMultipleExample
end
end
aasm(:work) do
aasm(:work, column: 'work_state') do
state :sleeping, initial: true
state :processing