Fork me on GitHub
#pedestal
<
2017-02-14
>
jimmy02:02:24

@mtnygard I find vase really interesting. It's super convenient to build fast backend API backend by datomic. I will try it out soon this week 😄

ikitommi18:02:58

@mtnygard have you thought of conforming with different wire formats as JSON & Transit have different capabilities for presenting data.. Haven’t seen that (runtime conforming) part on the spec roadmap. Here’s something we are doing for it: https://gist.github.com/ikitommi/fb3e0200504dd8b635ed7edd0cdbc768#runtime-coercion.

ddeaguiar18:02:46

I think conformance and coercion are two different concepts but they can be related by using s/conformer. I think that strongly couples coercion to your spec definition, though. I could be mistaken.

ikitommi19:02:35

Problem is that there is no coercion in spec. I’m using a special conformer, which doesn’t transform anything by default, only if you tell it to (do JSON or String -conversions). Another way would be to take a spec and transform it into a differently conforming spec, e.g. User -> UserJSON, UserString. Currently not 100% proof due to the global spec registry. But something needs to be done IMO. I would be glad if I could toss away my current code for this.

mtnygard21:02:20

@ikitommi Are you talking about this in the context of Pedestal in general or of Vase specifically?