uriparse-rs icon indicating copy to clipboard operation
uriparse-rs copied to clipboard

Implementation of RFC3986 including URIs and URI references.

Results 9 uriparse-rs issues
Sort by recently updated
recently updated
newest added

It addresses #21 It uses [`smol_str::SmolStr`](https://docs.rs/crate/smol_str/latest) as string invariant for owned segment, and `&str` for borrowed. `smol_str` is dependable, as it is maintained by rust_analyzer team, and used in it...

Hello, thanks for great work. It would be great if it uses a smallstring variant as backend for `Segment`. example crates are `smolstr`, `smartstring`, `kstring`, etc. `kstring` also provides a...

The string "/:" should be a valid URI reference with only a path according to RFC 3986, but parsing it with `uriparse` results in an error "schemeless path URI reference...

```rust use uriparse::{URI, URIReference}; fn main() { let base = URI::try_from("scheme:foo1/foo2").unwrap(); let reference = URIReference::try_from("./..//bar").unwrap(); let target = base.resolve(&reference); println!("target = {:?}", target); } ``` ``` $ RUST_BACKTRACE=1 cargo run...

Would be nice if other packages could access the list of schemes you maintain.

T-Feature/Enhancement
S-In Progress
P-Low
E-Easy

See https://tools.ietf.org/html/rfc6874

T-Feature/Enhancement
S-In Progress
P-Low
E-Medium

This repo doesn't have the text "URL" in the description, or topics, so this search wont find this repo: https://github.com/search?q=url+language:rust also some crates have URL keyword: https://github.com/servo/rust-url/blob/v2.2.2/url/Cargo.toml#L12 this one does...

P-Low
T-Documentation
E-Easy
S-Won't Fix

I'm interested in replacing `url::Url` with `uriparse-rs::URI` in the `lsp-types` crate. https://github.com/gluon-lang/lsp-types/issues/261#issuecomment-1750367878. But that would require `URI` to implement `PartialOrd` and `Ord`. `Url` does this by simply comparing the stringified...

Closes: https://github.com/sgodwincs/uriparse-rs/issues/6 This is based on #25, please only consider the top commit. (But I'm using that PR in testing already; sadly there seems to be no way to tell...