fix: timestamp will work with named machine #739
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes sure timestamps work also with named machines. Which currently is not the case.
Using timestamps on a named machine like so:
Will result in an error:
The fix is simple, in
ts_setter = "#{aasm(aasm_name).to_state}_at="
it was just missing the aasm_name as an argument. It missing tried to use thedefault
state machine which did not exist.Tests are updated,to use the timestamps functionality with a named machine. Let me know, if you would prefer for the test to be more explicit about what it checks.
btw: Really love the addition of timestamps, thx to @jaynetics !