This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-13
Channels
- # announcements (2)
- # babashka (2)
- # beginners (112)
- # calva (29)
- # cider (33)
- # clj-kondo (41)
- # cljdoc (10)
- # cljs-dev (2)
- # clojure (72)
- # clojure-berlin (3)
- # clojure-europe (10)
- # clojure-italy (6)
- # clojure-nl (15)
- # clojure-spec (5)
- # clojure-uk (40)
- # clojurescript (1)
- # clr (6)
- # community-development (6)
- # core-async (21)
- # cursive (42)
- # datascript (12)
- # duct (6)
- # flambo (1)
- # fulcro (50)
- # jobs (1)
- # leiningen (3)
- # off-topic (16)
- # re-frame (6)
- # reagent (23)
- # reitit (7)
- # ring-swagger (14)
- # shadow-cljs (35)
- # tools-deps (39)
- # vim (12)
How do you guys normally deal with looking into network calls from your front end to back end in Fulcro apps? All my stuff is through a centralized handler /api
, but when inspecting network on that its a mess of query language and makes things a bit hard to parse
the network tab in the fulcro chrome extension is really easy to understand IMO
@U09FEH8GN I have the issue where the tool doesn’t detect my app as being connected. Any ideas on how to debug that?
uninstall and re-install it
the chrome extension
@wilkerlucio Any tips on debugging fulcro-inspect when it says the app isn’t connected? I’m trying to start using this tool now over dirac
Uncaught ReferenceError: framework is not defined
at element_picker.cljs?rel=1568400659924:12
(anonymous) @ element_picker.cljs?rel=1568400659924:12
dom_history_viewer.cljs?rel=1568400661217:20 Uncaught ReferenceError: framework is not defined
at dom_history_viewer.cljs?rel=1568400661217:20
(anonymous) @ dom_history_viewer.cljs?rel=1568400661217:20
client.cljs?rel=1568400661606:342 Uncaught ReferenceError: framework is not defined
at client.cljs?rel=1568400661606:342
@njj the only think I can remember is double checking if you are using the preload
, because that's what triggers the start
you can also try to call yourself so you can follow it closely, are you using Fulcro 2 or 3?
@wilkerlucio I’m using a pre-react 16 version
so, this is what needs to be called from the client to start it: https://github.com/fulcrologic/fulcro-inspect/blob/master/src/client/fulcro/inspect/preload.cljs#L4
(notice this must be called before the fulcro app is initialized, otherwise it will not get it)
are you still unable to have the app shown in inspect right?
so if I find a way to call that (fulcro.inspect.client/install {})
myself, it could help figure out whats going on
@wilkerlucio it appears to be loading correctly w/ the preload
stuff, I tested it out by calling the above fn before the app started and I got the same errors.
I never tried with dirac, I don't know much dirac so I dont understand how that may affect things
it should work with Figwheel, but to be honest I have not used that in a long time
Interestingly enough one of the calls is Cannot read property 'call' of undefined
when trying to call (fulcro.inspect.client/install {})
yeah, strange, that framework message doens't help much
the element picker is the only real UI thing that the inspect client has, but it still a very simple thing (with no external deps, expect react itself and some google closure things)
there is some parts supposed to support both react pre and post 16: https://github.com/fulcrologic/fulcro-inspect/blob/master/src/client/fulcro/inspect/ui/element_picker.cljs#L74-L75
are source maps not working with figwheel? are they enabled for you?
if we had the cljs lines that could help
oh, but now that I read carefully, seems like its point to the cljs source, but at a defsc
line? :thinking_face: (that has only CSS)
that makes no sense 😛
yeah, and that's a defsc with just css definitions
can you try bumping fulcro?
what version do you recommend? Anytime I try to get into react 16 my entire app starts crapping 🙂
I dont remember if latest fulcro versions work with react prior 16, so may worth trying, you could for 2.8.13
and see what happens
if breaks, try getting one minor down, that will 8, 7 and 6
yeah right when I go to 2.6.0-RC1
which is where react-16 starts, everything starts failing
Is there a recommended way to render anything from any component into a singleton, like a modal? Like react portals? I thought about Dynamic Queries and Unions, but then I would have to implement the way how content renders in this singleton component.