check code for external mutations
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
https://forum.flow.com/t/update-on-cadence-1-0/5197#adoption-90
check code snippets for external mutations and rewrite them with entitlements
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 by reading the linked Cadence 1.0 adoption update, then search the documentation for code snippets that use external mutations. Identify each affected example and determine how the issue's requested entitlements apply; done means the relevant snippets have been rewritten and remain consistent with the documented Cadence behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100