[Feature] Allow customization of special schemes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 406
- PR merge metrics
- No merged PRs in 30d
Description
- Note that this crate implements the URL Standard not RFC 1738 or RFC 3986
I would like to work with some non-special schemes (gemini, gopher...) but get the same behaviour as if they were special, like IPv4 hosts and no empty hosts. I understand it's not standard, but it would be useful in many cases. A compile-time setting wouldn't even require any change to the API.
Would this be considered? I am willing to create a PR if needed.
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 reviewing the crate's handling of special and non-special schemes against the linked URL Standard. Define how a compile-time setting would make schemes such as gemini or gopher use special-scheme behavior, including IPv4 hosts and disallowing empty hosts, then establish tests that distinguish the configured behavior from the standard default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100