-
Notifications
You must be signed in to change notification settings - Fork 69
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
Drop cheshire for clojure.data.json #306
Labels
Comments
expez
added a commit
that referenced
this issue
Jun 27, 2021
expez
added a commit
that referenced
this issue
Jun 27, 2021
expez
added a commit
that referenced
this issue
Jun 27, 2021
expez
added a commit
that referenced
this issue
Jun 27, 2021
expez
added a commit
that referenced
this issue
Jun 28, 2021
expez
added a commit
that referenced
this issue
Jun 29, 2021
expez
added a commit
that referenced
this issue
Jul 1, 2021
vemv
pushed a commit
that referenced
this issue
Jul 1, 2021
vemv
pushed a commit
that referenced
this issue
Jul 1, 2021
vemv
pushed a commit
that referenced
this issue
Jul 1, 2021
vemv
pushed a commit
that referenced
this issue
Jul 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've had some issues with
cheshire
in the past. It's also a library with a ton of dependencies compared toclojure.data.json
which is entirely self-contained.clojure.data.json
recently went through a round of performance tuning and is now faster thancheshire
on some payloads and within spitting distance on most others.The big payload from clojars is read as
edn
andcheshire
is only used on the comparatively small payloads for maven central. I expect this change to:The text was updated successfully, but these errors were encountered: