theupdateframework / theupdateframework/rust-tuf
move tuf::client::PathTranslator to FileSystemRepository
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
tuf::client::PathTranslator allows clients to use an alternative path separator, but according to https://github.com/theupdateframework/specification/issues/63#issuecomment-556995907, the targets metadata path separators should always be /. So it makes more sense that the PathTranslator be a property on tuf::repository::FileSystemRepository, since it's the only thing that really needs to map target paths to files on a file system.
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
Start by locating the definitions and usages of tuf::client::PathTranslator and tuf::repository::FileSystemRepository, then trace how target paths are translated before reaching the filesystem. Done means the translation responsibility is attached to FileSystemRepository, client-facing target metadata paths remain slash-separated, and existing behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100