Using AsyncStorage, is there a way to deploy one’s app with a pre-built DB?

Some background: I have a hash-map datastructure of 15k static entries that I’d like to bundle with my app. Currently I store this in a JSON file that I require on app boot with (js->clj (js/require “path-to.json”)), which loads too slowly. My idea was to instead transform the JSON data to some reasonable datastructure that could be statically bundled and loaded on boot from AsyncStorage, removing the parsing time from the 5mb large JSON file

@looveh you need to write native module

@pesterhazy I also tried to use :value first but because of these problems we did the same as @misha there (using :default-value - which is actually not a proper model-view binding anymore...). fortunately we never had to change the value of an already rendered input field.

@knotschi, somebody should write a blog post about this

@pesterhazy can you describe an update already mounted component use case in more details? from my pov, component enclosing text-input either has local state, or accepts text-input value as an argument. in both cases, if state gets changed - text-input gets updated.

yeah that's what I mean

and as long, as ui is responsive and does not stutter - I don't really care (and, honestly, don't really know ) if it is done by means of re-usint text-input, or creating new one on every key stroke.

however

I noticed weird artifact on some inputs: when you clear it up with backspace (or whatever key is on visual kb) - it often leaves letter g or some other letter, as if it was a placeholder, but it is actually input text. and I can't delete it. but I did not spend any time to debug this yet.

reloading simulator helps, but not for long

@misha what do you mean by "create new one on every stroke"?

rn might unmount current text-input with old value, and mount another text-input with a new value

no

I didn't bother to figure out whether this is actually the case or not

they update existed

even with :default-value instead of :value?

with default value thay not update anything

of course if you not update defaultValue

that's the thing: if you use default-value instead of value - input does not lag, when you type too fast

that's right, because things happened in native side and nothing going through bridge

exclude change event

there is not re-render

nice

https://twitter.com/dan_abramov/status/785519293756764160