-
Notifications
You must be signed in to change notification settings - Fork 83
Fix: Escape URL before converting to URI; catch Addressable::URI::InvalidURIError #100
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
Fix: Escape URL before converting to URI; catch Addressable::URI::InvalidURIError #100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nudded Thank you so much for taking the time to improve Wasabi!
I made minor detail test-related comments, you can react to them, and then we can probably get this merged. If you don't have strong feelings either way, we can merge it and move from there.
❤️
@olleolleolle thanks for the quick reply! I've applied your suggestions, I agree with your comments 👍 |
2e26c5e
to
ed5ac2b
Compare
@olleolleolle I rebased and fixed the specs, hopefully, that will allow for a quick release 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Thanks for all the care & effort to improve this.
@nudded I came up with one more hurdle! It's a good one - add a CHANGELOG line in this change. (You need to rebase on master first, since I added a section there, for "Unreleased".) If you don't get around to it, I'll make a change myself later. |
4e6a4c0
to
7d59f83
Compare
This allows urls with spaces in, as they were previously re-escaped (in v3.5.0) We now also catch the Addressable::URI::InvalidURIError, as that might be raised while escaping if URI is invalid
7d59f83
to
d07b1d3
Compare
Done 🎉 |
This allows urls with spaces in, as they were previously re-escaped (in v3.5.0)
We now also catch the Addressable::URI::InvalidURIError, as that might be raised while escaping if URI is invalid