Deprecate http4s-json4s #4370
Merged
Deprecate http4s-json4s #4370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rossabaker
force-pushed
the
deprecate-json4s
branch
from
d3d9290
to
2d26480
Compare
hamnis
approved these changes
Feb 9, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
There is no public momentum toward a json4s port on Dotty.
jawn-json4sin Dotty compat mode conflicts with the Dottyjawn-fs2, so there is no way to nurse it along in 0.22 without copying code. The interest is estimated less than 5% of http4s-circe. The http4s team recommends Circe for JSON.If no volunteer steps up by February 13 to fix and maintain the http4s-json4s modules, we will proceed with this deprecation and removal from series/0.22 and main.
If a new maintainer does emerge for these module, note that the plan is to spin them off into their own repo: #4140