OData / OData/odataorg.github.io
Need clarity on Permissions propagation policy.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 73
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Given a type hierarchy of X.F.A where X.F is specified as Permission="read" and X.F.A is specified as Permission="write".
There is disagreement about whether X.F.A may be written. Our assertion is that permissions may be removed, but not added when moving towards the leaves in a type hierarchy, and thus a write to X.F.A would fail. Others are asserting the opposite.
The documentation within Org.OData.Core.V1.xml needs to be clarified to make the propagation policy clear.
Contributor guide
No contributing guide indexed for this repository
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
Open Org.OData.Core.V1.xml and locate the documentation for Permission propagation through type hierarchies. Review the X.F and X.F.A example and the surrounding permission definitions, then resolve the stated disagreement with maintainers before updating the wording. Done means the documentation explicitly describes the propagation policy and makes the example's outcome unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100