Otto Chrons
Otto Chrons
Do you have a simple reproduction for this? Sounds like some implicit coming from Boopickle might cause it, but the stack trace doesn't really give any details.
The internal representation of Scala classes and data structures is not as straightforward as in vanilla JS, so the plugin would not be able to show the data in a...
Ping @cornerman
Workaround is not to use the macros 😄
Dude! Sharing is caring! 😏
One alternative would be to provide `shapeless` bindings for BooPickle, like they exist for Circe. But I haven't used shapeless, so don't have the knowledge to do it.
@japgolly is it ok if I just copypaste the relevant code from your macro-utils to keep boopickle dependency-free?
Hm, yea, I suppose the macro doesn't surround the generated names with backticks or something. Damn you Scala for having all these complications 😆
First of all you should never have a pickler defined with `implicit def` because that will regenerate the pickler every time it's used :) Otherwise it's probably a duplicate of...
As a workaround before the problem is fixed, you can prevent the creation of the binary gz file by ``` cd dist touch dio-fullstack.gz chmod -w dio-fullstack.gz ``` after building...