This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-15
Channels
- # beginners (97)
- # boot (54)
- # cider (13)
- # cljs-dev (3)
- # cljsrn (9)
- # clojure (64)
- # clojure-berlin (1)
- # clojure-brasil (119)
- # clojure-dev (3)
- # clojure-france (5)
- # clojure-greece (1)
- # clojure-italy (5)
- # clojure-madison (1)
- # clojure-russia (15)
- # clojure-spec (25)
- # clojure-uk (57)
- # clojurebridge (5)
- # clojurescript (45)
- # code-art (1)
- # community-development (17)
- # cursive (24)
- # datomic (83)
- # emacs (11)
- # fulcro (70)
- # hoplon (7)
- # immutant (3)
- # leiningen (19)
- # luminus (5)
- # lumo (25)
- # onyx (123)
- # other-languages (7)
- # pedestal (2)
- # re-frame (12)
- # ring (15)
- # ring-swagger (51)
- # shadow-cljs (89)
- # spacemacs (23)
- # sql (4)
- # unrepl (57)
- # utah-clojurians (1)
- # vim (1)
has anybody successfully built navigation features using https://github.com/seantempesta/cljs-react-navigation
Have you checked the example project: https://github.com/seantempesta/cljs-react-navigation/tree/master/examples/re-frame/uiexplorer
Yes i did and followed what was done there, but kept getting "screen should be a react element" Used all possible ways (reactify etc, but wasn't successful
Weird, do you have the same setup in terms of npm package versions and reagent versions etc?
There were version issues and i have resolved it.
The approach that you had taken worked for me.
adapt-react-class ...
thanks a lot
I keep getting "shoudl be a react element" even though i tried reactify etc