Stuck on an issue?
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.
Remove dependency on circe-generic
See original GitHub issueCirce instances could and should be hand-written, currently it should be easy to do with Decoder.forProduct2 and the corresponding Encoder function.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
circe-generic-extras
This library provides configurable generic derivation and other functionality extending the generic derivation mechanisms provided in Circe's circe-generic ...
Read more >json - Using snake case without explicit Configuration ...
It's perfectly possible. It's a trade off: if you have implicits in your companion objects, you don't have to import them; if you...
Read more >Circe - A JSON library for Scala powered by Cats
circe depends on cats instead of Scalaz, and the core project has only one dependency (cats-core). Other subprojects bring in dependencies on Jawn...
Read more >circe/circe - Gitter
what if I don't want to drop null keys, I just want None to exclude? @travisbrown here's the exact error: https:// ...
Read more >Circe is driving me insane : r/scala
This issue can only be avoided by removing current implicit from the scope that is ... _ // for @JsonKey import io.circe.generic.semiauto.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Basically what @calvinlfer said, plus the fact that it brings a dependency someone might not want to have, as well as shapeless which is quite large.
it is never a good idea to use auto generation because if a user comes in and changes a case class, they will change the JSON unknowingly. It’s better to disconnect them like this so you end up with some sort of a compile error if you add or remove fields