Skip to content
Open
Changes from all commits
Commits
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
3 changes: 1 addition & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1012,12 +1012,11 @@ Since version *3.0.13* AASM supports ActiveRecord transactions. So whenever a tr
callback or the state update fails, all changes to any database record are rolled back.
Mongodb does not support transactions.

There are currently 3 transactional callbacks that can be handled on the event, and 2 transactional callbacks for all events.
There are currently 3 transactional callbacks that can be handled on the event, and 2 transactional callbacks for all events:

```ruby
event before_all_transactions
event before_transaction
event aasm_fire_event (within transaction)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ovedanner I do agree, the method aasm_fire_event shouldn't be mentioned here. But we still need an indicator to show that this is the time when the actual event is fire. Maybe replacing the line with

                  <event fired>

would help? What do you think?

event after_commit (if event successful)
event after_transaction
event after_all_transactions
Expand Down