Atomicity of creating a resource and its ACL
@csarven is already working on this.
Since May 17, 2021.
Assessment
This issue has not been assessed yet.
Description
With solid/specification#31 an ACL has to be created after the resource, and until it does, the inherited ACL is used. It may be problematic if more restrictive permissions is required when a resource is required in a permissive container.
- Dominant language
- HTML
- Stars
- 131
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from solid/web-access-control-spec
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
solid/web-access-control-spec#140 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
solid/web-access-control-spec#139 · 6 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
solid/web-access-control-spec#137 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/web-access-control-spec#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/web-access-control-spec#135 ·