Plans to migrate from JSONb? #2

Closed
LeifW opened this Issue Sep 10, 2011 · 2 comments

Projects

None yet

2 participants

@LeifW
LeifW commented Sep 10, 2011

Are there plans to switch this from JSONb to aeson? I hear aeson is the new hotness.
Currently, JSONb is tied to attoparsec 0.8, blocking the upgrade of things which depend on attoparsec 0.9 (e.g. Yesod 0.9) for repackaging that only allows one version of a package at a time. Ideally, JSONb would be upupdated, but then mention of AESON on the JSONb hackage page makes it sound deprecated.
If you don't have time, and don't think it would be too involved, I might try taking a stab at it?

@snoyberg
Owner

I have no plans, but i would definitely accept a pull request.

On Saturday, September 10, 2011, Leif Warner <
reply@reply.github.com>
wrote:

Are there plans to switch this from JSONb to aeson? I hear aeson is the
new hotness.
Currently, JSONb is tied to attoparsec 0.8, blocking the upgrade of things
which depend on attoparsec 0.9 (e.g. Yesod 0.9) for repackaging that only
allows one version of a package at a time. Ideally, JSONb would be
upupdated, but then mention of AESON on the JSONb hackage page makes it
sound deprecated.
If you don't have time, and don't think it would be too involved, I might
try taking a stab at it?

Reply to this email directly or view it on GitHub:
#2

@LeifW
LeifW commented Sep 11, 2011

Even simpler, looks like JSONb's been updated to support attoparsec 0.9 (it was just a cabal file limit). Sorry for the noise.

@LeifW LeifW closed this Sep 11, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment