JSONAPI-Resources / JSONAPI-Resources/jsonapi-resources
No clear way of scheduling jobs / doing anything outside the main transaction
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.3k
- Forks
- 546
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there is no clear way of scheduling jobs, or doing anything other outside of the main transaction in every request. There has been a Issue on this, but it is no longer relevant due to changes in the OperationsDispatcher.
While there is an after_process_operations callback on the controller, how to get any data on the updated/created/viewed resource is not clear from the docs, and also not immediately clear from the source.
Any information on this would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
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 controller's after_process_operations callback and the OperationsDispatcher, then compare the current source with the existing documentation. Clarify how data for updated, created, or viewed resources can be accessed and how work can be scheduled outside the main transaction. Done means the documented guidance answers these use cases without relying on the superseded issue 503.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 34/100