Global atomicity requirements
Open
Nobody has claimed this yet.
topic: resource access
topic: resource life cycle
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
It may be worthwhile to be explicit about global atomicity requirements in the spec and refer back to it where applicable:
- creation of containers in path component
- deletion of resources
- other lifecycles..
Potential errors should be reported from general (eg. can create nested containers?) to specific (eg. can modify target resource?)
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 specification sections covering container creation, resource deletion, and other lifecycle operations. Map where atomicity requirements and error handling are currently described, then make the requirements explicit and ensure errors are ordered from general capability checks to target-resource checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100