Doing some experimenting with using Pathom for server-side rendering:
that's interesting - what role does pathom play in SSR ? Curious to know
It's helpful for breaking your pages apart into small individual pieces without those pieces needing to do a bunch of duplicated database queries/logic. e.g. in this example, the :ui.shell/app resolver needs to query for the current user's email address, but the top-level resolver (`:ui/subscriptions`) doesn't need to know about that. And if :ui/subscriptions also needed to query for something from the user's document, pathom would make sure that the user document only gets queried for once.
i find it interesting that you are outputting html snippets instead of data through resolvers. Didn't think of that at all 😄
haha yeah it was kind of a light bulb moment, took a while before it occurred to me
Doesn't ui/subscriptions "know" about it through ui.shell/app?
:ui/subscriptions doesn't need to query for :user/email and then pass that to :ui.shell/app. I.e. components need to specify their direct dependencies, but they don't need to query for transitive dependencies.