This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-25
Channels
- # admin-announcements (2)
- # beginners (36)
- # boot (37)
- # cider (65)
- # cljsrn (92)
- # clojars (3)
- # clojure (225)
- # clojure-austin (5)
- # clojure-belgium (2)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-greece (2)
- # clojure-mexico (3)
- # clojure-news (2)
- # clojure-quebec (1)
- # clojure-russia (14)
- # clojure-spec (24)
- # clojure-uk (53)
- # clojurescript (34)
- # cursive (14)
- # datascript (9)
- # datomic (4)
- # defnpodcast (8)
- # devcards (30)
- # dirac (7)
- # editors (7)
- # emacs (1)
- # figwheel (1)
- # hoplon (85)
- # immutant (2)
- # incanter (1)
- # luminus (5)
- # off-topic (41)
- # om (18)
- # onyx (11)
- # perun (2)
- # re-frame (11)
- # reagent (9)
- # ring (3)
- # spacemacs (2)
- # spirituality-ethics (1)
- # test-check (19)
- # testing (12)
- # untangled (14)
- # yada (9)
Hey folks! Quick question if anyone is around. I have a list of things, where the ID is in a dropdown. I have it structured
Root->Dropdown->Dropdown-item
. Now I have a table to show more info on a specific item that’s structured Root->Table
. Is the proper way to do this having 2 query endpoints on the server, one for :dropdown
and one for :table
?
It's really up to you. The app client database has to be structured for the UI queries, but using load-data you can query however you like, and then use a post-mutation to re-form the views of the queried data for the UI.
Awesome, that's what I was hoping. Thanks for your work!
Anthony left a good comment though that there's another similar line of code that seems to have the same bug I fixed,
@jasonjckn: it is in the SNAPSHOT version...I believe I pushed that. Not a formal release yet