In om.next with a react native Navigator, I'm trying to change scene/screen in response to a click, but find I have to capture and rebinding *reconciler* etc, which doesn't seem right. Should the navigation be done inside om/transact! instead? or some other way?
I have a situation where a root component calls a transaction mutating some part of the state it doesn't have in it's query which a sub component asks for. The problem is that the mutation initiated by the root leads to a re-read with the sub components query. Yet the sub component does not re-render with the new app-state, although it's query contains a key mentioned in my transaction. See https://gist.github.com/SMeister/df825c11e958a26e741e.
Are there any examples to do forms with input fields in om.next? I’m thinking about using a component for each input field doing all the validation and so on. I see only Davids Todo MVC example were he has one TodoItem Component which handles all the editing in local state.