Optionally include cached file path in metadata returned from pin_meta
Open
Nobody has claimed this yet.
.ux
- Dominant language
- Python
- Stars
- 59
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
If a cache is being used--likely should be a subfield on Meta
(Alternatively it's very easy for the board to tell you where the cached file is?)
board.fs.hash_name(path, True)
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 at the pin_meta entry point and inspect the Meta structure, then read board.fs.hash_name(path, True) to understand how cached paths are currently determined. Clarify the intended metadata shape and behavior when no cache is used; done means the API consistently exposes the cached file path without breaking existing metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100