Fork me on GitHub
#cljsrn
<
2016-12-22
>
levitanong00:12:48

@raspasov: I updated to 8.2.1. Also re-natal and now I'm getting a "var undefined: self" error. Even after downgrading to 8.2. No idea what's going on. @[email protected]

levitanong00:12:03

Was good opportunity for me to play around with boot-react-native at least!

raspasov00:12:20

Did you try Clean Xcode?

raspasov00:12:32

Clean the project

levitanong00:12:50

yup, done that. even cleaned project folder. lein clean

levitanong00:12:01

even react-native upgrade

raspasov00:12:36

Hmmm annoying screen shot? Is the error in the simulator

levitanong01:12:09

@raspasov when I react-native log-ios it says the error originates from line 19, but doesn’t say what file. However, if I check figwheel-bridge.js, on line 19 there is var self;. Though I can’t imagine why it complains about not finding something it’s declaring.

jorda0mega01:12:20

is there any documentation on how to add externs in boot-react-native?

levitanong01:12:34

@jorda0mega i think in the example there is a place they set aside for you to put the externs.

jorda0mega01:12:36

@levitanong yeah I was wondering about that file but do I just put the name? a path? url?

levitanong01:12:20

You’re basically declaring the names that should be preserved

jorda0mega01:12:13

let me try that. thanks for the help @levitanong

levitanong01:12:36

no problem. 🙂 just message me again if you need more direct help, and then we’ll go through the file you want externed.

jorda0mega01:12:08

thank you 🙂

jorda0mega02:12:57

so I’m trying to include firebase through cljsjs-firebase but I have noticed that the output of this module to the build folder only has a minimized .js file. Whereas other modules such as react include both a .cljs and .js file. Does anybody know why this might be?

jorda0mega02:12:51

apparently something to do with version 3.5.3 of cljsjs-firebase. version 3.2.1 seems to work fine

leontalbot19:12:14

@misha Hi! I read from one of you prior threads, regarding Datascript: >I am doing something similar now as an experiment – maintaining cache harold of datascript db with a bi-directional subscription to changes. >this way you have data in DS for normalization and super easy server sync, + instant UI updates, because mutations are done to cache, not DS >but I have yet to see how it'll go on a larger scale.

leontalbot19:12:29

Any updates on that?

levitanong19:12:11

how would DS be easy for server sync? Wouldn’t you have to implement custom merge and transform incoming server data to a form that the ds transact! can use?

levitanong20:12:03

Ah, I remember that. Haha!

misha21:12:43

@leontalbot, no, have to take care of lots of business logic at the moment, but I'll publish any valuable updates here, when I get back to it.

misha21:12:13

I even forgot how it works now, did not touch that code for a few months already

leontalbot21:12:10

Thanks for the follow up

misha21:12:03

@leontalbot what exactly do you expect to hear about that approach? what I can tell right now, is: the only 2 DS features/things I use are: 1) easy sync with datomic, 2) pull (entities into cache hash-map). I don't use any query capabilities, which makes me sad a bit. Basically, all the app code is about updating/reading from cache hashmap, like if you'd keep all the data in an atom.

leontalbot21:12:16

The discussion started in the exponent slack group, in the clojurescript channel. @tiensonqin simply asked: "Anyone using datascript on React Native?"

leontalbot22:12:08

I wanted myself to know that, and made some research. I found that people are saying it is not performing well on mobile

leontalbot22:12:18

then I say your thread and was curious

misha22:12:29

probably not in the "all in" fashion, because of performance (unless small dataset)

misha22:12:40

I will have huge dataset on client in production for offline use, so it was very easy for me to accept "cache" solution, instead of trying to optimize the shit out of queries, etc.

leontalbot22:12:30

Anything open sourced I could see?

misha22:12:39

current implementation is not even extracted to a separate thread/js machine