Custom auto-save feature
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.2k
- Forks
- 644
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I use custom versioning in model, so it can't be just saved with .save1. It should be save through custom method like: .update_by_user(user, attributes).
Describe the solution you'd like
I want to have posibility to customise auto-save process. Implement it by my self.
Describe alternatives you've considered
Right now i could monkey-patch aasm to archive that.
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
No file, test, or entry point is named. Start by tracing AASM's auto-save behavior and how model persistence is invoked, then compare it with the requested custom method such as update_by_user(user, attributes). Done should include a defined customization path and tests demonstrating that auto-save can use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100