-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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.
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
net/url: add URL.RawFragment, like RawPath #37776
Comments
Adding to the proposal minutes. This seems fairly unobjectionable given the precedent set by RawPath. If anyone thinks we shouldn't do this, please speak up. Thanks. |
Based on the precedent from RawPath and the lack of any objections, this seems like a likely accept. |
No change in consensus (still crickets here), so accepting. |
Change https://golang.org/cl/227645 mentions this issue: |
OpenAPI and JSONSchema do fancy things with the fragment including
funny path operations that distinguish between a literal / and an escaped %2f.
Just like happened with Path, the solution is probably to add RawFragment,
with the same semantics for Fragment/RawFragment as Path/RawPath.
/cc @mpvl
The text was updated successfully, but these errors were encountered: