This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-28
Channels
- # 100-days-of-code (10)
- # announcements (2)
- # architecture (16)
- # beginners (51)
- # bitcoin (3)
- # calva (1)
- # cider (6)
- # cljdoc (8)
- # cljs-dev (14)
- # cljsrn (4)
- # clojure (59)
- # clojure-italy (26)
- # clojure-losangeles (1)
- # clojure-nl (13)
- # clojure-spec (54)
- # clojure-uk (81)
- # clojurebridge (4)
- # clojurescript (20)
- # core-async (16)
- # cursive (39)
- # datomic (27)
- # emacs (12)
- # events (1)
- # figwheel-main (20)
- # fulcro (35)
- # funcool (1)
- # graphql (9)
- # hyperfiddle (10)
- # jobs (1)
- # jobs-discuss (7)
- # keechma (10)
- # lumo (22)
- # nrepl (18)
- # off-topic (28)
- # onyx (3)
- # pedestal (4)
- # re-frame (8)
- # reagent (8)
- # ring (4)
- # rum (3)
- # shadow-cljs (29)
- # testing (5)
Is it possible to return a tempid mapping and some other data about that entity?
{::prim/tempids {payment-id db-id}
[:payment/by-id db-id] payment}
something like thator do i have to have a separate remote query afterwards?
@currentoor you can, it's a mutation join http://book.fulcrologic.com/#MutationJoins
Oh right, forgot those existed 😅
@jesse050 not out of the box yet. they are very compatible and pathom has some really cool stuff for fulcro + graphql
Tried it a bit, now stuck on something else but looks really prommising. Planning on having graphql as the bakend for the current app i'm working on
Is there any spinoff from Fulcro?
or some other OM-Next++ ?
https://github.com/forward-blockchain/qlkit this one is the only similar on I know of.
@jesse050 Pathom has a Fulcro remote that will automatically transform between GraphQL on queries: https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/fulcro/network.cljs#L184
just put that in as a Fulcro remote, and you should be able to hit GraphQL endpoints with normal Fulcro UI queries.
not heavily used yet, so may be slightly rough around the edges...but it isn't a lot of code. Maybe 200 or so lines gets you a remote that will mostly "just work". I think Wilker has some demonstration of this against github's API...don't remember where, though
@tony.kay sorry mr.kay, i forgot to input my query, so my css won't pass to the root hehehe
@claudiu Just our 2 cents about UI testing, we are actually started doing UI tests but we switch remotes for mock remotes.. Which makes the UI tests superfast and you can use it to catch browser bugs.
But we were already creating mock remotes because we are creating a demo environment so customers can try us out without starting a trials..
i might have to do something like that for demos also
The remote abstraction really shines for these use cases
@U060GQK8U sounds cool. How do you test the UI, on state or somth like image regression ) jest ?
We do normal state testing with clojure.test and we do very simple UI tests so we can make sure our most important flows always work. We haven't looked to much into image regression
@jesse050 https://github.com/awkay/pathom/blob/doc-improvements/docs/DevelopersGuide.adoc#GraphQL I’ve contributed docs to pathom for this. They’re not merged yet, but you can preview them there.
Just made an overview video showing off a demo that @wilkerlucio wrote to hit GitHub’s API, along with some of the Fulcro Inspect stuff you end up with as a result. https://youtu.be/Yk7xFry0w2Y
Released Fulcro 2.6.5 to clojars. This release has optimizations from @thheller that reduce code size for advanced optimization compiles by 1.5k per component.
@claudiu @tony.kay @wilkerlucio thanks for the replies. Will check out pathom