This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-01
Channels
- # adventofcode (1)
- # bangalore-clj (1)
- # beginners (8)
- # boot (47)
- # cider (6)
- # cljsrn (3)
- # clojure (155)
- # clojure-brasil (2)
- # clojure-china (3)
- # clojure-conj (1)
- # clojure-hk (4)
- # clojure-korea (36)
- # clojure-russia (38)
- # clojure-spec (53)
- # clojure-taiwan (1)
- # clojure-uk (14)
- # clojurescript (70)
- # clojurex (9)
- # component (2)
- # cursive (20)
- # datascript (19)
- # datomic (39)
- # defnpodcast (1)
- # events (5)
- # figwheel (2)
- # hoplon (81)
- # incanter (2)
- # jobs (7)
- # juxt (3)
- # klipse (1)
- # leiningen (1)
- # luminus (15)
- # mount (1)
- # off-topic (21)
- # om (5)
- # om-next (2)
- # onyx (19)
- # pedestal (2)
- # proto-repl (1)
- # proton (5)
- # re-frame (19)
- # reagent (4)
- # rethinkdb (2)
- # ring-swagger (6)
- # rum (13)
- # specter (6)
- # untangled (4)
- # yada (1)
Hi, I have some trouble to understand the local app-state in the untangled-template-workspace project. To be more precise with the “Pages” component. If I print out the current app-state (with log-app-state) all the defined pages e.g. main, login, new-user have the query and the data from all other defined pages and also the [:ui/fetch-state …] for each of them. Is this correct behavior or do I miss something? Compared to the Video Tutorial “Using Unions for Efficient Tabs/Routing" I don’t understand the duplication of those data.
Btw: What's the best practice or solution to design a dynamic multilevel navigation in the local app-database? For example something like that.
{:ui/locale "en-US"
:pages [{:id :page-a
:name "Page-A"
:icon "a-icon"
:sub-pages [{:id :sub-a
:name "Sub-A"
:icon "sub-a-icon"}]}
{:id :page-b
:name "Page-B"
:icon "b-icon"
:sub-pages []}]})
A typical use-case would be showing different navigations for different clients e.g. Desktop, Mobile.