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

Addressable gem dependency fix #301

Conversation

jsonenthusiast
Copy link

A new version of addressable gem is out (2.4.x). Without this fix, json-schema will not work with the latest version of the addressable gem.

jeromegl added 2 commits January 28, 2016 16:13
…on-schema will not work with the latest version of the addressable gem.
iainbeeston pushed a commit to iainbeeston/json-schema that referenced this pull request Feb 26, 2016
I've had to change one of the specs because of this. It seems that
addressable now raises an error if you parse a uri that looks like a
json text, which was one of our test cases.

This fixes and supersedes voxpupuli#301
iainbeeston pushed a commit to iainbeeston/json-schema that referenced this pull request Feb 26, 2016
I've had to change one of the specs because of this. It seems that
addressable now raises an error if you parse a uri that looks like a
json text, which was one of our test cases.

This fixes and supersedes voxpupuli#301
iainbeeston pushed a commit to iainbeeston/json-schema that referenced this pull request Sep 29, 2016
I've had to change one of the specs because of this. It seems that
addressable now raises an error if you parse a uri that looks like a
json text, which was one of our test cases.

This fixes and supersedes voxpupuli#301
iainbeeston added a commit that referenced this pull request Sep 29, 2016
I've had to change one of the specs because of this. It seems that
addressable now raises an error if you parse a uri that looks like a
json text, which was one of our test cases.

This fixes and supersedes #301
@iainbeeston
Copy link
Contributor

I'm going to close this now #312 has been merged

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