after callback not working in transition scope
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.2k
- Forks
- 644
- PR merge metrics
- No merged PRs in 30d
Description
event :run, after: :notify_somebody do
transitions from: :sleeping, to: :running, after: :notifi_somebody_else
Actual behaviour:
Record in notify_somebody method is in running state, but notifi_somebody_else is triggered when record is still in sleeping state.
Expected behaviour:
after callback is triggered after record changes state (is in running state)`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the event- and transition-level callback example in the issue and trace how AASM executes each after callback relative to the state assignment. Done means the transition-scoped callback observes the new state, while the event-level callback continues to behave as documented; add regression coverage for the reported ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100