This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-28
Channels
- # admin-announcements (1)
- # beginners (33)
- # boot (35)
- # braveandtrue (1)
- # cider (6)
- # cljs-dev (59)
- # cljsrn (24)
- # clojure (44)
- # clojure-austin (3)
- # clojure-china (1)
- # clojure-russia (13)
- # clojure-spec (63)
- # clojurescript (71)
- # community-development (1)
- # core-async (2)
- # cursive (6)
- # datomic (1)
- # editors-rus (2)
- # emacs (3)
- # hoplon (47)
- # jobs-discuss (3)
- # keechma (1)
- # lein-figwheel (2)
- # om (38)
- # om-next (4)
- # onyx (2)
- # other-languages (63)
- # parinfer (3)
- # planck (4)
- # re-frame (3)
- # reagent (2)
- # slack-help (4)
- # specter (26)
- # tmp-json-parsing (7)
- # uncomplicate (66)
- # yada (7)
There has been some interesting discussion about re-natal, react-native-boot, etc... Is anyone else thinking about eschewing babel and the react-native packager all together and writing a custom cljs packager for RN in clojure?
Anyone success with https://github.com/facebook/react-native-fbsdk?
link is fine, and both figwheel, react-native don't complain
@tiensonqin: we're using the fbsdk successfully (with 0.19)
I'm using 0.2.1
although we're seeing intermittent issues with it
@marc-schwartz: sounds interesting. What are you thinking of exactly?
I'm actually fighting with the react native packager myself, it's a strange (and largely undocumented) beast.
such complex, every corner is a trap
fbsdk for sign in is terribly complex, I couldn't agree more
but it works, so I'd move on with this
hehe that's my attitude as well
how's 0.26.2 for you?
I'm struggling big time trying to update boot-react-native to that version: https://github.com/mjmeintjes/boot-react-native/issues/49
@pesterhazy: just thinking that in dev-mode, the packaging server provides source files through http endpoints and code changes are published though a web socket. That is all our react native apps see... It should be possible to build source in memory with the Google Closure compiler and provide the compiled source to RN apps by providing the same api as the package server.
Interesting idea. I suspect that the packager needs to be involved anyway, because that's all the RN developers test with
But maybe you can do that in a single step, with one offline bundle that gets augmented by the cljs code?
I guess that's roughly how re-natal works
"ReactNativeJS: {:status 0, :status-text "Request failed.", :failure :failed}" is being thrown on a ajax.core
's GET
call, why?
(register-handler
:load-data
(fn [db _]
(GET ""
{:handler #(dispatch :process-data %1)
:error-handler #(.warn js/console (str %))})))
(register-handler
:process-data
(fn [db value]
(assoc db :data (str value))
(.warn js/console (str value))))
@debug: nope, no additional setup needed
@debug, cljs-ajax works great for me on boot-react-native