This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (13)
- # babashka (59)
- # beginners (58)
- # bitcoin (3)
- # calva (7)
- # cider (2)
- # cljsrn (4)
- # clojure (41)
- # clojure-dev (18)
- # clojure-germany (1)
- # clojurescript (14)
- # conjure (7)
- # cursive (5)
- # datahike (1)
- # graalvm (44)
- # jobs-discuss (3)
- # kaocha (19)
- # lsp (109)
- # luminus (3)
- # off-topic (8)
- # pathom (32)
- # re-frame (4)
- # reveal (3)
- # shadow-cljs (16)
- # spacemacs (5)
- # sql (18)
- # vim (13)
Hello 👋 what is the current pathom (esp. pathom3) + datomic story? I would love to give pathom a go and I’m looking for pointer re: a good place to start i.e. earn about using it with datomic. Is https://github.com/wilkerlucio/pathom-datomic something one can use with pathom3?
hello 🙂 most people doing serious work with this are integrating Pathom with datomic in a more manual way (writing specific resolvers for parts of the attributes)
I know @U06B8J0AJ and @U06KD64RX played with pathom-datomic, they may be able to give a better user experiencie, I created it most as an experiment, this is part of Pathom Dynamic resolvers, which is the next thing I'll be working in Pathom 3
ok, will have to experiment then, which is good as well 🙂 thanks @U066U8JQJ, the progress on pathom3 looks amazing, looking forward to seeing what’s next 🙂
We found pathom-datomic to be a really nice default to get up and running. We use that as a "baseline", in order to not write a resolver for every single attribute in the DB, and then switch to resolvers for things where we need to inject more intelligence.
Hi! Thanks so much @U06B8J0AJ. This is what I was thinking, starting out with pathom-datomic. Pathom3 looks tempting thought, esp. for a new/early stage project. Those two are incompatible though right? (i.e. pathom-datomic & pathom3)
I'm not sure @U7MHWDLD8, we haven't tried Pathom 3 yet. When you use Datomic, it's crucial that you can update the environment mid-mutation (since when you transact to Datomic, you need to get a new DB from the result, and inject it into the Pathom
env in order for subsequent resolvers to use the correct DB for responses). I'm not sure if Pathom 3 has that yet (@U066U8JQJ did take notice of this in a previous thread), but if it doesn't, I'd recommend sticking to Pathom 2 for the time being.
Alright! Will need to do some experimenting now I guess but this very helpful to get me started, thank you!
one thing to also consider is that Pathom 2 datomic support relies on
reader3, which I suggest everyone to avoid, its a dropped experiment in Pathom 2, the Pathom 3 port for that should be easy enough, I'm currently working on dynamic resolvers support (starting with GraphQL because its a harder problem and will get more things clear)
@U066U8JQJ Would you suggest that it's a better idea to go with Pathom 3 at this point, and just write the resolvers required, than to go with Pathom 2 + pathom-datomic + reader3?
at this exact point you couldn't use the Pathom Datomic with Pathom 3, the safe way to go still Pathom 2 + reader2 + manual resolvers.
reader3 has issues that were fixes in Pathom 3 already (bad planning in some situations) but not backported (because there is a lot of non Pathom 2 related things on the Pathom 3 impl). But I'm getting confident with the basics in Pathom 3, experiments have been running fine, and Datomic for Pathom 3 is right around the corner (I guess 1 week, 2 tops), Pathom 3 + Datomic dynamic will be probably safer than Pathom 2 +
> Datomic for Pathom 3 is right around the corner (I guess 1 week, 2 tops) that’s some good news, very exciting!
Thank you für pathom!!
I just upgraded from pathom 2.2.31 to 2.3.1. This causes a massive slowdown on my setup.
I have a fulcro app that queries for massively nested trees on load and then works with small changes afterwards.
I wrapped the parser with
time , which reports "Elapsed time: 3122.194217 msecs" with 2.2.31 and "Elapsed time: 429305.222488 msecs" with 2.3.1.
The fans start humming.
Is this a known issue? Should I start to debug or should I wait for 3.x and stick to 2.231 in the meantime?
I am using
last time I had a long talk with Tony, and we realised in the end the problem is that in this jump Pathom started using guardrails internally, and then when the user has Guardrails on it causes this kind of slowness in development
so yeah, Pathom now also pays guardrails price, and that makes slow in dev, but prod still the same
hello people, a bit of early news, very excited to say that Pathom 3 is now runnable in Babashka scripts! I'm super happy about it, this means we can now use Pathom engine to make scripts that run blazing fast!
this needs to be merged before it fully works, but if you use git deps and point to my commit there it works https://github.com/fulcrologic/guardrails/pull/21
Smart Maps currently don't work, given they require Potemkim, which uses a ton of weird features that Babashka doesn't support, I'm investigating if its possible to make a separate simpler implementation that works in Babashka
(also requires the latest babashka snapshot, that you can download from #babashka-circleci-builds)