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.
Move circe-spray to its own project
See original GitHub issuecirce-spray is now the only published module that we can’t build for 2.12, and since Spray seems to be more or less unmaintained at this point I think it makes sense to split circe-spray into its own project.
The result would look similar to what I’ve just done for circe-jackson. I’d prefer to maintain history, so the first step would be a fresh clone of this repo and then something like this:
git filter-branch --subdirectory-filter modules/spray/
Once this is done I’d probably vote to de-aggregate hygiene and benchmark and get rid of sat-doge altogether.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 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
Done (here and here). Thanks again @n4to4!
@n4to4 Wow, that was fast! Looks good to me—I’ll set up circe/circe-spray and make you a co-maintainer.