This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-03
Channels
- # adventofcode (91)
- # announcements (7)
- # aws (3)
- # babashka (69)
- # beginners (46)
- # calva (30)
- # cider (12)
- # clj-kondo (88)
- # cljs-dev (11)
- # cljsrn (1)
- # clojure (195)
- # clojure-dev (21)
- # clojure-europe (2)
- # clojure-italy (13)
- # clojure-nl (56)
- # clojure-spec (4)
- # clojure-sweden (6)
- # clojure-uk (27)
- # clojurescript (179)
- # core-async (2)
- # cryogen (1)
- # cursive (2)
- # data-science (1)
- # datomic (57)
- # fulcro (15)
- # graalvm (9)
- # instaparse (6)
- # joker (18)
- # juxt (9)
- # leiningen (6)
- # off-topic (20)
- # other-languages (10)
- # pathom (5)
- # re-frame (20)
- # reitit (2)
- # rewrite-clj (5)
- # shadow-cljs (78)
- # sql (34)
- # tools-deps (128)
- # uncomplicate (16)
- # vim (6)
if there a branch or something of pathom where graphql fulcro remote works with Fulcro 3?
seems to be using Fulcro 2 namespaces currently
@roklenarcic should be easy to implement a fulcro-remote in fulcro3. "just a function"
well I can implement anything, the issue is that I told other people that fulcro 3 had graphql integration through pathom, which turned out to be untrue
@roklenarcic its not untrue, this didn;t really change between 2 and 3, the only difference is that there is no pre-made Pathom parser to hook into the Fulcro network on f3, but that's something quite trivial to implement