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

Workaround for HTTParty 0.8.1 #22

Merged
merged 2 commits into from
Apr 4, 2012
Merged

Conversation

edave
Copy link
Contributor

@edave edave commented Jan 3, 2012

Here's a workaround that allows Neography to still use HTTParty 0.8.1 (until your ticket w/ Neo4J is addressed) by subclassing HTTParty's Parser to use Crack instead of MultiJSON. Or basically, it's the best of reverting to HTTParty 0.7.8 but still maintains compatibility with HTTParty 0.8.1 (which other gems, like aws-sdk require)

@edave
Copy link
Contributor Author

edave commented Jan 3, 2012

Forgot to say that this approach is encouraged by HTTParty - see this example and this issue

@maxdemarzi
Copy link
Owner

Thanks for this workaround David. I'm hoping it get's fixed upstream, but if not I'll definitively merge this in.

maxdemarzi added a commit that referenced this pull request Apr 4, 2012
Workaround for HTTParty 0.8.1
@maxdemarzi maxdemarzi merged commit fddb7cb into maxdemarzi:master Apr 4, 2012
@maxdemarzi
Copy link
Owner

Thanks David, I finally got around to pulling this in.

willkessler pushed a commit to willkessler/neography that referenced this pull request Apr 21, 2014
added methods to get the outgoing/incoming aliases of a relationship
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