@seantempesta: head’s up display is enabled. It does not work same way as in browser because it is tied to DOM, but luckily it also logs compilation problems to the console, and therefore shown in a “yellow box” on the screen. So yes, fakeLocalStorageAndDocument is also used to enable head’s up display.

@artemyarulin: did not realise you improved the code from original figwheel-react-native that much, great stuff! At some time I will try deep dive in your code and try to implement these improvements in re-natal

@drapanjanas: Thanks - I did it basically as a exercise in order to understand better figwheel-react-native (didn’t want to have something that I don’t understand), but it turns out after couple of month I forgot much of the things I thought about contributing things back, but I’m using CLJS, meaning for example I can use goog.Deferred directly, while with JS you have to implement some kind of shims for that, etc. In any case - feel free to ping me

@artemyarulin: Am giving your repo’s a spin now. The template nicely rounds things up. Well done!

Hi, I was wondering if there's a way to avoid the janky updates in a TextInput field when using re-frame in a re-natal project?

I'm calling dispatch from the :on-change-text event handler, and the data comes from a subscription set to the TextInput's value property. When running on a physical iOS device you can see the character appear, flicker etc each time you type. Also any spelling errors will have the red underline hidden as you carry on typing, but clicking on the word will show the normal correction options.

Other than that I'm really enjoying how quickly it's possible to make apps in clojurescript!