Use Sequelize transactions where appropriate
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
As mentioned by @jazcarate in #62, we should use https://sequelize.org/v3/docs/transactions/ throughout the code base (where it's appropriate)
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 discussion in issue #62 and the linked Sequelize v3 transactions documentation. Inspect the codebase's database operations to identify paths where transactions are appropriate; done means those relevant paths consistently use transactions, with no specific files or tests named in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100