This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-12
Channels
- # adventofcode (112)
- # architecture (1)
- # beginners (55)
- # boot (26)
- # cider (19)
- # cljs-dev (19)
- # cljsjs (1)
- # cljsrn (7)
- # clojure (140)
- # clojure-android (3)
- # clojure-austin (3)
- # clojure-china (3)
- # clojure-gamedev (1)
- # clojure-greece (43)
- # clojure-spec (75)
- # clojure-sweden (5)
- # clojure-uk (21)
- # clojurescript (66)
- # core-async (2)
- # core-logic (1)
- # cursive (63)
- # datascript (5)
- # datomic (4)
- # devcards (2)
- # duct (13)
- # editors (5)
- # emacs (9)
- # figwheel (4)
- # fulcro (42)
- # graphql (25)
- # immutant (7)
- # jobs (29)
- # leiningen (13)
- # lumo (7)
- # numerical-computing (3)
- # off-topic (22)
- # om (2)
- # onyx (25)
- # pedestal (3)
- # re-frame (14)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (3)
- # rum (12)
- # shadow-cljs (9)
- # uncomplicate (1)
- # unrepl (6)
I thought you were trying to do a highlight…once you have :main
, isn’t that what you needed?
I’m sorry I wasn’t clear enough. I just though that maybe I could modify my query:
[{[r/routers-table :top-router] [::r/current-route]}]
so that it would just get me the screen out of the returned data bound in the arg vector in defsc. I think it would be too much magic though 🙂
Instead I have the query as above and I use (get-in props [{[r/routers-table :top-router] [::r/current-route]}])
and then extract the keyword I am interested in.
Starting into videos on going full-stack. Still very basic, but getting towards a fully-functional full-stack app.
ok, got something 🙂 https://github.com/fulcrologic/fulcro/pull/97
you are a quick recorder man, I took a full day to get my last video on 30 min XD
@wilkerlucio and you're a fast implementor...tests and all 🙂
thanks, now I'm pretty much dead XD
thanks for the feedback, yeah, I agree this is all vital and we need to test against all of it
about the targeting, where can I find the code that handles the target special types?
humm, I think I just founded
so, maybe we should move this logic out so it can be used in more places?
anyway, I'm dead, going sleep here, talk tomorrow, cya 🙂
The source code and files for the YouTube videos are now on github at https://github.com/fulcrologic/fulcro-basics-videos
@wilkerlucio Yep, that's the function...we can move it if it makes a circular dep...otherwise I think it is well-placed. It is related to targeting incoming data, which is what you're doing, and it is in impl, since it really isn't meant to be public API (`integrate-ident` is that).
https://github.com/fulcrologic/websocket-demo/blob/master/src/main/websocket_demo/server.clj#L56
I noticed there is an empty file in fulcro https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/client/core.cljc why is this? shadow-cljs does not like this at all
@mitchelkuijpers its just a warning, shouldn’t interfere with actual use. would be good if the empty file was removed though. 😉
No I noticed, but still very weird. It should at least have a ns
declaration
But thnx though @thheller 😉
@a.espolov yes and yes, I dont have the details but you should be able to find info about both on the docs
given that fulcro 2.0 doesn't use om.next and thus isn't supported by pathom, what approach would you recommend for server reads?
@mitchelkuijpers oops. My bad
@tpliliang Please use the developer's guide. It covers all of that.
@roklenarcic Wilker and I are working on the strategy for supporting om next libraries, and pathom in particular. I may release a lib here in the next day or two that defines om-next symbols and points them to their Fulcro equivalent. That would let you use a number of libs since the external API compatibility should be quite good.
@adamvh they are separated packages, you have to add each