Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade http4s module from 0.21 to 0.23
See original GitHub issueNot upgrading will prevent projects who use pure config from upgrading to http4s 0.23, example below:
[error] * org.http4s:http4s-core_2.13:0.23.0-RC1 (early-semver) is selected over 0.21.24 [error] +- org.http4s:http4s-dsl_2.13:0.23.0-RC1 () (depends on 0.23.0-RC1) [error] +- org.http4s:http4s-server_2.13:0.23.0-RC1 () (depends on 0.23.0-RC1) [error] +- org.http4s:http4s-blaze-core_2.13:0.23.0-RC1 () (depends on 0.23.0-RC1) [error] +- org.http4s:http4s-client_2.13:0.23.0-RC1 () (depends on 0.23.0-RC1) [error] +- com.github.pureconfig:pureconfig-http4s_2.13:0.16.0 (depends on 0.21.24)
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It would be nice to release also a version of pureconfig depending on http4s
0.22in the meantime 🙏Totally agree 😃 Would a PR with a new pureconfig-http4s-022 module be accepted if I go ahead and create it? Does not seem to be something tremendously difficult, but will make lives of some folks easier.