Skip to content

Fix URI resolution with scheme-only URI #82

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

Merged
merged 1 commit into from
Jan 9, 2022
Merged

Fix URI resolution with scheme-only URI #82

merged 1 commit into from
Jan 9, 2022

Conversation

sigmavirus24
Copy link
Collaborator

Prepare for 2.0 release which drops support for 2.7, 3.3, 3.4, 3.5, 3.6
and sets the foundation for better future development practices
(declarative packaging configuration, pre-commit enforcement, etc.)

Closes #81

Verified

This commit was signed with the committer’s verified signature.
sigmavirus24 Ian Stapleton Cordasco
Prepare for 2.0 release which drops support for 2.7, 3.3, 3.4, 3.5, 3.6
and sets the foundation for better future development practices
(declarative packaging configuration, pre-commit enforcement, etc.)

Closes #81
@sigmavirus24 sigmavirus24 merged commit 2d0317b into master Jan 9, 2022
@sigmavirus24 sigmavirus24 deleted the bug/81 branch January 9, 2022 15:59
@aucampia
Copy link

aucampia commented Jan 9, 2022

Thank you very much for the quick feedback and fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Resolving a relative URI Reference against a base with only an authority does not work
2 participants