graphprotocol / graphprotocol/docs
Mention handlers are atomic
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 85
- Forks
- 162
- Avg merge
- 6h 31m
- Merged PRs (30d)
- 4
Description
Might be a useful info to know that changes made in a handler are cached in memory and applied to the store at the end, making them atomic in effect
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
Search the documentation for the existing handler and store sections, since no file or test is named. Add a clear note explaining that handler changes are cached in memory and applied to the store at the end, and confirm the wording fits the surrounding documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100