so we would have to move it, and make sure that it affects extra-routes only if it should be based on the content type (or something similar?)

OK, so there was no real problem with Untangled Spec. It was an unexpected very strange thing in the tests for Untangled Client

We were mocking bits of Om internals to test behaviors, and somehow Om was getting confused in the process

wow interesting,

so is there a new snapshot i need to pull?

i assume you're referring to https://github.com/untangled-web/untangled-spec/issues/2 right

not referring to diff bug, this is untangled-client mocking an om rendering function

kk

@jasonjckn: okay i figured out the problem with the diff algorithm

a bit weird, but it should be fixed

nice!

thanks

on clojars?

you’d have to ask tony as we’re on a snapshot right now

I can push it...is it on github>

yup

its on develop

k

spec?

0.3.8-SNAPSHOT now up

thanks

working beautifully