@cjmurphy why do you need the timeout?

just so you get other content to render before the load response comes back?

That's right. Otherwise (it seems) loading was taking over and the UI was not getting a chance. Within the component render method I'm just checking some props and if they are not there doing the (dom/div "Loading").

I was not seeing "Loading" until I put the timeout in. There was evidence that the "Loading" path was being taken, but it was so fleeting that "Loading" could not be seen.

This seems like a strange error message to me: "The required namespace "taoensso.sente" is not available, it was required by "fulcro/websockets.cljs"." What I mean is should I have to include sente as a dependency? Just wanting to know if that is the intention. Usually libraries take care of their own dependencies don't they (don't use "provided")?

@cjmurphy The intention is that if you don’t use Fulcro’s server stuff, you don’t get the deps.

It intentionally does dynamic lib requires, and that is documented

so yes, if you use anything server-like from Fulcro, you need to require the libs for ring, sente, etc.

http://book.fulcrologic.com/#Websockets <- it's the first thing it says here, will read...

just curious - are the docs always the latest, or is there a way to get the older versions?

I think the book is quite good at at going through the changes that happened with different versions. So I would say the docs are intended to be used at their latest.

@nha I do try to mention deltas…and I also try hard not to make changes that break things. The book is in DevelopersGuide.adoc in fulcro github, so it is versioned

oh, and all releases are tagged as well

The make file in fulcro has the commands to build the HTML for the book

i’m already using datomic, but should i use pathom to convert datomic refs to fulcro idents?

or just do that by hand myself?

I’m getting back into fulcro and using datomic as well. I’m sticking with pathom to make sure I have a consistent interface in case i need to grab any non-datomic stuff. Been mucking around with some ideas for utilities to take advantage of the om-next/pull fidelity to reduce pathom wiring for my default cases

@eoliphant yeah probably a good idea

if possible please share any good ideas you come up with

@currentoor convert to idents? The server has to send non-normalized data, so idents are probably wrong if that’s where pathom is being used

or do you mean convert refs to db idents into keywords?

(e.g. for enums)

@tony.kay oh your totally right!

oops

i’m just now getting to entities across references on the server and i forgot it’s supposed to non-normalized 😅

@currentoor pathom is about processing the query, it doens't normalize anything 😉 but yeah, keeping pathom will give you an extension engine to work on top of datomic data like other people already said 🙂

@tony.kay i have a situation where if i don’t specify initial-state on a component then the props are not correct, but simply adding :initial-state {} makes the props behave correctly

is this expected behavior? perhaps we should throw an error or warning?

My understanding is that specifying {} will give you a table record, perfect for a :singleton defsc. And not specifying anything - well you won't even get a table, let alone a record in that table.

turns out that was actually not the issue this time, but i have noticed some hard to debug weirdness with initial-state sometimes