argonaut json macro

Kenji Yoshida @xuwei_k

argonaut json macro https://t.co/5Ua7okDzxg https://t.co/vgYtmQmega

Travis Brown @travisbrown

.@xuwei_k Nice! Have you looked at `Liftable`? Here's a quick implementation that should work in both 2.10 and 2.11: https://t.co/ku1OmpWitf

Kenji Yoshida @xuwei_k

@travisbrown I didn't know `Liftable`. thanks!

Travis Brown @travisbrown

@xuwei_k You get more flexibility in how you define them with macro bundles in 2.11 (and a nice `Liftable.apply`, etc.) /cc @den_sh @xeno_by

Mark Hibberd @markhibberd

After an epic battle with scalac there is an argonaut 6.0.4 release for scala 2.11.0-final: https://t.co/15ivZyzikY (Thanks to @xuwei_k )

Travis Brown @travisbrown

@xuwei_k By the way, any plans for macro-generated Argonaut codecs (like Play's Inception)? It's on my list of things to do. /cc @mandubian

Miles Sabin @milessabin

@travisbrown Ahem ... TypeClass and/or LabelledGeneric ;-) /cc @xuwei_k @mandubian

Travis Brown @travisbrown

@milessabin Yep, `LabelledGeneric` is what I was thinking. Anyone in particular working on this, @seanparsons? /cc @xuwei_k @mandubian

S @seanparsons

@travisbrown @milessabin @xuwei_k @mandubian I'm moderately busy on the Haskell port, so will probably see a TH implementation first. :)

Travis Brown @travisbrown

@mandubian Yes—it's very impressive! (I still do want the type-provider-y `Lens[Contact].informations` syntax, though.) /cc @skaalf @xuwei_k

Mark Hibberd @markhibberd

@travisbrown @milessabin @seanparsons @xuwei_k @mandubian I have a start. Will push up the code. Just not enough time at the moment.

Mark Hibberd @markhibberd

@travisbrown @milessabin @seanparsons @xuwei_k @mandubian https://t.co/JBbx5nh30l EncodeJson works, haven't looked at DecodeJson yet.

Mark Hibberd @markhibberd

@travisbrown @milessabin @seanparsons @xuwei_k @mandubian It is sitting to the side for the moment but plan is to move it to companion.

Travis Brown @travisbrown

@markhibberd This works, but watch out for colliding `derive`s: https://t.co/S7lES82V2W /cc @milessabin @seanparsons @xuwei_k @mandubian

Travis Brown @travisbrown

@milessabin It's not funny! I don't know how many times I've seen "error: not found: value LabeledGeneric"!

Travis Brown @travisbrown

@milessabin By the way, thoughts on avoiding collisions without `import AutoDecodeJson.auto.{ derive => deriveDecodeJson }`-ing everything?

Mark Hibberd @markhibberd

@travisbrown @milessabin I was thinking about that, is it reasonable to just add something to the each companion explicitly with unique name

Mark Hibberd @markhibberd

@travisbrown @milessabin And not expose the shapeless `.auto` one at all. Seems like one of the few options anyway.

Mark Hibberd @markhibberd

@milessabin Another q, is there a sensible way to expose LabelledGeneric macro in a way that would let them specify custom label mappings.

Mark Hibberd @markhibberd

@milessabin I.e. implicit def CustomEncodeJson: EncodeJson[Custom] = derive("fieldOne" -> "field_1", "fieldTwo" -> "field_2")

Miles Sabin @milessabin

@markhibberd You could take the approach I tried in BlueEyes: https://t.co/pE07tQzpGj. I used an explicit schema value to map names etc.