Cache or eTag resources in /assets folder
Open
Nobody has claimed this yet.
feature
P3
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
We currently eTag / cache resources included in the component repos but do not offer any cache mechanism for resources in /assets. The same mechanism could be applied:
- known assets included in the
index_templateare fingerprinted using the same versioning / last_modified logic withversion=0.0.0 - assets that are not requested through the
index_templaterevert to using eTag
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 by locating the existing eTag and cache handling for resources included in component repositories, then trace how /assets resources are served and how the index_template identifies known assets. Verify that template assets use fingerprinting with version=0.0.0 and that other assets use eTags, with tests covering both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100