Skip to content
This repository has been archived by the owner on Feb 12, 2025. It is now read-only.

Is this gem still being actively supported? (JSON parse bug) #26

Open
stefan-lz opened this issue Jul 3, 2014 · 2 comments
Open

Is this gem still being actively supported? (JSON parse bug) #26

stefan-lz opened this issue Jul 3, 2014 · 2 comments

Comments

@stefan-lz
Copy link

Hi Thomas,

Just wondering if you are still supporting this magnificent gem?

I'm using it for my app: http://topstack.io, but just hit a massive bug, where response could not be parsed as it was encoded in ASCII not UTF8.

I guess it could just be my environments reading the response as ASCII, instead of UTF8. For now I've forced it to encode in UTF8 and submitted a pull request if others have this problem: #25

Cheers,

@stefan-lz stefan-lz changed the title Is this gem still being actively supported? Is this gem still being actively supported? (JSON parse bug) Jul 3, 2014
@thomas-mcdonald
Copy link
Owner

Hi Stefan - I never really gave this gem the maintenance it needed when I first released it and since I've not actively been developing against it there's a few different bugs/issues I've not fixed.

I'm planning on rewriting a v2 of the gem over the summer with support for the write API as well, probably simplifying some of the internals as I go along.

@stefan-lz
Copy link
Author

Ok cool, I guess this gem is palliative care until then (I know - bad joke).

👍 to v2

Let me know if you need help developing/testing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants