Feedback: /runtime/reference/deno_json/ - Needs Improvement
- Dominant language
- TypeScript
- Stars
- 204
- Forks
- 385
- Avg merge
- 14h 49m
- Merged PRs (30d)
- 7
Description
## Documentation Feedback
**Path:** [/runtime/reference/deno_json/](https://docs.deno.com/runtime/reference/deno_json/)
**Helpful:** No ❌
**Feedback:**
> Explain how named permission sets interoperate with individual permissions: do they widen them? Narrow them? Does the last permission overwrite all previous ones?
**GitHub User:** @tredondo
---
*This issue was automatically created from the documentation feedback system.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the documentation page at /runtime/reference/deno_json/ and review how named permission sets and individual permissions are described. Verify their precedence and interaction, then update the page so it clearly explains whether permissions widen, narrow, or overwrite one another; done means the documented behavior answers each question in the feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100