This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-06
Channels
- # announcements (1)
- # beginners (147)
- # boot (9)
- # calva (28)
- # cider (3)
- # circleci (18)
- # cljdoc (54)
- # cljs-dev (55)
- # cljsrn (22)
- # clojure (179)
- # clojure-canada (9)
- # clojure-dev (74)
- # clojure-europe (1)
- # clojure-italy (15)
- # clojure-nl (7)
- # clojure-spec (30)
- # clojure-uk (55)
- # clojurescript (65)
- # core-async (15)
- # cursive (12)
- # datomic (16)
- # events (4)
- # fulcro (25)
- # graalvm (3)
- # joker (2)
- # kaocha (15)
- # keechma (94)
- # off-topic (12)
- # qlkit (2)
- # re-frame (15)
- # reagent (11)
- # reitit (29)
- # remote-jobs (15)
- # rewrite-clj (16)
- # shadow-cljs (73)
- # spacemacs (151)
- # sql (3)
- # tools-deps (11)
- # unrepl (19)
- # vim (35)
Can anyone recommend an approach to async storage. I want some durable storage so that users can work offline and post data to the server when the network is available.
We've ended up defaulting to firestore / datastore for this across several web and RN projects
The asyncstorage documentation says "It is recommended that you use an abstraction on top of AsyncStorage instead of AsyncStorage directly for anything more than light usage since it operates globally."
My default position is "a few helper functions seem to suffice - wait till I out grow them" but perhaps that's short sighted.
i have similar questions so will be following this. Are there any cljs rn examples online for offline app usage?
I am trying to use components from 'react-native-elements' in my re-natal app. I have installed the package with yarn add
and im tring to load a component with (def Header (js/require "react-native-elements/Header"))
then go through the rest of setup (start-figwheel ... )
and (def rne (js/require "react-native-elements"))
and then
(def header (r/adapt-react-class (.-Header rne))