Consider centrally defining all users of the blob URL store
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
Description
Letting the blob URL store be extended doesn't seem like a good idea. At least, I think there's general agreement it's not the best pattern and we don't want to see it spread further.
We should enumerate all objects which can be stored in it and what policies affect them, rather than allowing arbitrary extensions.
Raising this separately from #92 as that's a big enough task on its own.
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
No files, tests, or entry points are named. Start by locating the blob URL store and every object currently stored in it, then review the policies affecting those objects. Done means the store's supported objects and applicable policies are centrally enumerated and arbitrary extensions are no longer the intended pattern.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100