Clojurians Log v2

https://twitter.com/swannodette/status/882939815741849600 nice shoutout ^^

So, I think @adambros and I figured out a way to make it possible to compose into the client-side om-next parsing (of reads). The mutations will still need to use our multimethod (which already makes it composable). I have to do some experiments, but this could be pretty exciting, as it would allow for targeted parsing customization on the client, and easier incremental porting from stock om.next.

@tony.kay nice, I'm interested to see how that would go, in which cases you see that being useful? I mean, I made a couple of apps with Untangled and I never felt the need to extend the client parser, IMO keeping it standard is being an advantage since I don't have to think on special hoops while debugging the data

so I wonder in which cases you see it being an improvement

I doubt standard Untangled users would need it..though it would make parameter parsing possible, which we cannot do currently.

I kind of like the model as it is, but the other significant thing is there is no easy way to port from standard Om Next to Untangled at the moment. This would make it possible to do an incremental port. Not high on my priority list at the moment, but it was a cool find.

gotcha

I’m working on a new website. Feedback would be very welcome: https://awkay.github.io/untangled/