This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-05
Channels
- # bangalore-clj (1)
- # beginners (50)
- # boot (72)
- # cider (53)
- # cljs-dev (303)
- # cljsrn (2)
- # clojure (403)
- # clojure-conj (3)
- # clojure-dev (7)
- # clojure-italy (18)
- # clojure-russia (129)
- # clojure-sg (1)
- # clojure-spec (44)
- # clojure-uk (25)
- # clojurescript (112)
- # core-async (4)
- # core-typed (3)
- # cursive (23)
- # datomic (114)
- # defnpodcast (1)
- # emacs (1)
- # figwheel (2)
- # graphql (18)
- # hoplon (110)
- # instaparse (6)
- # jobs (3)
- # jobs-discuss (10)
- # leiningen (5)
- # luminus (1)
- # lumo (151)
- # off-topic (22)
- # om (3)
- # om-next (3)
- # onyx (4)
- # parinfer (1)
- # pedestal (8)
- # precept (51)
- # re-frame (19)
- # reagent (3)
- # ring (1)
- # ring-swagger (5)
- # spacemacs (21)
- # sql (25)
- # test-check (2)
- # uncomplicate (8)
- # unrepl (33)
- # untangled (20)
- # yada (14)
because right now I got to a point where I have different app-state :data on each :page change but this doesn't trigger a re-render, basically if I press on page 2 it stays with page2 data rendered, even though app-state :data changes subsequently
(tbody
(for-tpl [d data]
(single-data-row :d d))
(div :class "row"
(div :class "col-md-12
d-flex
justify-content-center
dash-pag-nav")))
also, I'm doing the ajax-request function when the route changes to #some-table-list but with a page param, perhaps that's why it's not triggering a re-render ... although app-state :data IS changing ...
@flyboarder how did you go? any progress?
oh, i was asking about something else actually 🙂
i think we need to see what single-data-row
is doing to help more with ^^
well here it is
(defelem single-data-row [{:keys [d]} _]
(tr
(td (:name @d))
(td (:name_2 @d))
(td (:address @d))
(td (:email @d))
(td (a (img :src (:image @d)))
(td (a :href (str "#manage?id=" (:id @d))
"Manage")))))
@avabinary yay 🙂
yeah, if in doubt, just wrap it in a cell=
you'll get the feel for what really needs it and what doesn't as you practise
oh dang, hadn’t realized that happened
re discourse, i’ll figure it out with micha
@micha do we want to perhaps move to another host? i was looking and 20/mo seems on the pricy side
or perhaps we could set up a way to chip in
i imagine it would
we coudl perhaps start by putting it behind DNS we own
and maybe they have stuff set up to do the redirects etc
someone can also go through all the questions and extract valuable stuff into Github wiki… someone with a lot of free time
the furthest i’ve gotten is https://github.com/hoplon/hoplon/wiki/Hoplon-Overview
i think moving away from .cljs.hl will be good for learning and teaching, i felt it really complicated explanations of everything
i had an idea about javelin the other day
first-classing the graph
(def g (graph)) (.cell g 123)
and graphs can’t depend on eachother, you get exception
the idea is that you often want to make isolated machines in components, and can run into difficult perf/bug territory because what you do in there can have global implications if you accidentally wire to something else
you could also call (.destroy g) and then accesses/resets to cells in g are exceptions
even better
in my ide thing i am thinking that when you delete a cell from the graph its value becomes an exception
totally, or FL
i think you can address it if the dependency exceptions show a path to the original
like a stack trace kinda
i can imagine hovering over it and it telling me which of its dependencies was also ERR
and if there is an exception while evaluating the formula then it will evaluate to #ERR
would ERR have metadata on it about the exception/provenance?
i suppose it must for the ide to do its thing
@thedavidmeister yes I have made some progress
Long time no see :P
@thedavidmeister I am working on getting you a code snippet
data -> sorted data -> indexed data -> lense
so from my abstraction of this, I think we can generalize both the sort and index of the data, and provide a single cell that would handle these cases for us
I’ll throw a few variations on that sort in hoplon/brew
I think the take away here is that all of the state should be contained within the tracked cell for -tpl macros, if you need to modify state then that cell needs to be a lense, otherwise move the portion that changes state into an element and use that element in the macro
I ended up splitting the two steps apart as I think indexing a collection is generally useful for cells, indexed-cell
will only index the data while sorted-cell
will sort+index the data
if you need custom sorting sorted-cell
has a signature for sort
which is used with sort-by
as a keyfn