Skip to content

Guide for keeping state column in sync. #554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mehmetaydogduu wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Guide for keeping state column in sync. #554

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -605,6 +605,20 @@ end

You could also use a calculated column or view in your database.

Also if you wish to prevent the state column from going into an asynchronous values with the state machine you can force it to sync with rails validates. In your model file:

```ruby
enum state: OrderStateMachine.states.collect { |s| [s,s]}.to_h # It is recommended to use string enum.
validates :state, inclusion: { in: states.values }, allow_nil: true
define_method(:set_initial_state) { self.state = self.current_state if self.state.nil? }
after_initialize :set_initial_state, if: :new_record?
validate :state_in_sync?
private
def state_in_sync?
errors.add(:state, :invalid, message: 'is not equal current_state', strict: false) unless state == current_state
end
```

### Accessing metadata from the last transition

Given a field `foo` that was stored in the metadata, you can access it like so:
Expand Down