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.

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

Accept that parsing downcases the scheme part, allow Addressable 2.6 #133

Merged
merged 3 commits into from
Feb 7, 2019

Conversation

dentarg
Copy link
Collaborator

@dentarg dentarg commented Feb 6, 2019

This is the situation since Addressable 2.6: sporkmonger/addressable#281

Close #132

This is the situation since Addressable 2.6: sporkmonger/addressable#281

Close #132
@dentarg
Copy link
Collaborator Author

dentarg commented Feb 6, 2019

Does this require another major bump? 😬

Something changed, but I don't think it is particular breaking.

@dentarg dentarg changed the title Parsing downcases the scheme part Accept that parsing downcases the scheme part, allow Addressable 2.6 Feb 6, 2019
spec/lib/twingly/url_spec.rb Outdated Show resolved Hide resolved
@walro
Copy link
Contributor

walro commented Feb 7, 2019

Something changed, but I don't think it is particular breaking.

I don't know honestly. But seeing we're probably the only ones on version 6 I think we can go with 6.1 or even 6.0.1 here if we decide the previous behavior was a bug :)

@dentarg
Copy link
Collaborator Author

dentarg commented Feb 7, 2019

We have always downcased the scheme when normalizing, and I would argue that is in that situation it matters, when you want to compare URLs. Not sure what more one can do with URLs, other than "use" them, e.g. connect to them, and that should still work. That's my reasoning at least. :)

@dentarg dentarg merged commit bf19d12 into master Feb 7, 2019
@dentarg dentarg deleted the allow-addressable-2.6 branch February 7, 2019 09:22
@walro
Copy link
Contributor

walro commented Feb 7, 2019

Sounds reasonable.

dentarg added a commit that referenced this pull request Mar 4, 2019
To release #133.
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.

None yet

2 participants