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

Use MultiJson and MultiXml for parsing instead of Crack #89

Merged
merged 2 commits into from Sep 13, 2011
Merged

Use MultiJson and MultiXml for parsing instead of Crack #89

merged 2 commits into from Sep 13, 2011

Conversation

alexfrydl
Copy link
Contributor

I've switched the parser to use MultiJson and MultiXml, which automatically chooses the best option from what is installed, or optionally what is explicitly specified, allowing the use of Yajl or nokogiri or what have you instead of requiring parsing be done with Crack.

@DAddYE
Copy link

DAddYE commented Jul 12, 2011

+1

1 similar comment
@nesquena
Copy link

+1

@tcocca
Copy link

tcocca commented Jul 13, 2011

+1 for sure

@hypomodern
Copy link

+1

@jimmycuadra
Copy link

This is sorely needed. Crack chokes on some valid responses that the stdlib JSON handles correctly. One such example is here: #75

@ralph
Copy link

ralph commented Jul 31, 2011

+1 Before applying this patch, I got all kinds of encoding errors while using the Google Translate API. With this patch applied, no issues any more. Either this one or:
#92

@ericgj
Copy link

ericgj commented Aug 2, 2011

+1

@nbibler
Copy link

nbibler commented Aug 4, 2011

+1 from me, too.

I'm seeing similar issues with HTTParty 0.1.8 and Ruby 1.9.2-p290 giving the Psych::SyntaxError from /lib/crack/json.rb:12:in 'parse'.

@RyanScottLewis
Copy link

+1

4 similar comments
@czarneckid
Copy link

+1

@iriya
Copy link

iriya commented Aug 23, 2011

+1

@sunteya
Copy link

sunteya commented Aug 25, 2011

+1

@dleavitt
Copy link

dleavitt commented Sep 7, 2011

+1

@jnunemaker jnunemaker merged commit 05cacfe into jnunemaker:master Sep 13, 2011
@danbronsema
Copy link

Fantastic! Everything is working better than expected now!

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