theupdateframework / theupdateframework/rust-tuf
Hide Windows file path compatibility behind a feature flag
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
There's a lot of path names that illegal because of FAT/ Windows compatibility. Someone might not like this since they are only deploying to *nix. Some of the checks could be hidden behind a feature flag.
These restrictions apply to both TargetPath and MetadataPath.
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 validation for TargetPath and MetadataPath and identify which restrictions enforce FAT/Windows compatibility. Determine how an optional feature flag should control those checks, then verify that Unix-only deployments can disable them while the default behavior remains compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100