Skip to content

Conversation

@binarycleric
Copy link
Contributor

@binarycleric binarycleric commented Jun 6, 2025

Pull Request

Summary

This is an issue with how urljoin worked in that if a URL contained a path in the first parameter it would be excluded when the join took place. Our test coverage didn't check for this kind of condition initially.

Fixes #W-18725788


What Changed

Using yarl to handle URI parsing.


Checklist

  • I’ve added or updated unit tests where necessary
  • I’ve added or updated documentation
  • I've run pdoc3 to generate the documentation
  • I’ve manually tested the functionality in this PR
  • This pull request is ready for review

Testing

# Example
pytest
python examples/your_example.py

This is an issue with how urljoin worked in that if a URL contained a
path in the first parameter it would be excluded when the join took
place. Our test coverage didn't check for this kind of condition
initially.
@binarycleric binarycleric marked this pull request as ready for review June 6, 2025 16:42
@binarycleric binarycleric requested a review from a team as a code owner June 6, 2025 16:42
@binarycleric binarycleric merged commit fc2b529 into main Jun 6, 2025
5 checks passed
@binarycleric binarycleric deleted the fixing-uri-parsing branch June 6, 2025 16:49
binarycleric added a commit that referenced this pull request Jun 6, 2025
This is an issue with how urljoin worked in that if a URL contained a
path in the first parameter it would be excluded when the join took
place. Our test coverage didn't check for this kind of condition
initially.
binarycleric added a commit that referenced this pull request Jun 6, 2025
This is an issue with how urljoin worked in that if a URL contained a
path in the first parameter it would be excluded when the join took
place. Our test coverage didn't check for this kind of condition
initially.
binarycleric added a commit that referenced this pull request Jun 6, 2025
This is an issue with how urljoin worked in that if a URL contained a
path in the first parameter it would be excluded when the join took
place. Our test coverage didn't check for this kind of condition
initially.
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.

2 participants