Add documentation under modeling for the use-cases unlocked by having a system type
Open
Nobody has claimed this yet.
documentation
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 105
- Avg merge
- 10h 35m
- Merged PRs (30d)
- 17
Description
These include:
- Support, Global Admin & other roles
- Create for types with no upper level parent
- Allowing access for all objects of a certain type
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 in the modeling documentation area and review how system types are currently described. Document the listed use cases: Support, Global Admin and other roles; types without an upper-level parent; and access to all objects of a type. Done when these use cases are clearly explained under modeling.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100