I'm trying to do this tutorial https://anmonteiro.com/2016/02/routing-in-om-next-a-catalog-of-approaches/ Despite having the :value {:keys [:app/route]} on mutate method, I need to transact [(change/route! {:route :app/home}) :app/route] go get :app/route updated. Is this the expected behavior? Where I can read more about :value on mutate?

@souenzzo https://github.com/omcljs/om/wiki/Om-Next-FAQ#what-does-value-keys--do-from-a-mutation-result-map

anyone know if there are plans to cut a release that includes react 16 support?

So, it seems to me that set-state! always causes an invocation of the parser via reconcile! (if the component has access to the reconciler, which it seems it usually does). This seems incorrect to me. The pendingState gets put in place by the lifecycle stuff. Anyone know why a reconcile needs to run?

Perhaps it is a bug in reconcile!, but my reading of that code makes it impossible to not run the query engine.

And my devcard experiment with logging in the parser reads confirms that set-state! triggers a read of props