Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exhaustive, in-one-place API reference is positively needed. Referring to RFC is not enough. #27

Open
rulatir opened this issue Sep 1, 2023 · 0 comments
Open

Exhaustive, in-one-place API reference is positively needed. Referring to RFC is not enough. #27

rulatir opened this issue Sep 1, 2023 · 0 comments

Comments

@rulatir
Copy link

rulatir commented Sep 1, 2023

I am trying to migrate from another URL parser to this library. There are differences between that and this library with respect to the host-related values (specifically inclusion vs. exclusion of :<port> in the value). It would be super convenient to have each property and its exact semantics documented exhaustively at hand, instead of being referred to an RFC and having to wade through standardese.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rulatir