Fork me on GitHub
#om
<
2016-09-25
>
levitanong12:09:41

@anmonteiro in om-next-fullstack, how is it that the #js reader macros don’t throw errors when run from clj? 😮

anmonteiro12:09:24

btw I “fixed” your issue yesterday: https://github.com/omcljs/om/pull/785

levitanong12:09:44

oh! Hurrah! 😄

levitanong12:09:25

re: data_readers… sorry, i’m pretty new to this. I’m guessing boot isn’t getting that bit of data.

levitanong12:09:02

I don’t suppose i can just copy and paste it in my boot task? 😛

anmonteiro12:09:05

ahhh, yeah, that’s a known problem

anmonteiro12:09:58

that’s boot.core/load-data-readers! btw

anmonteiro12:09:28

maybe that should be documented, happy to take a PR adding that to the readme

levitanong12:09:54

@anmonteiro Awesome thanks man! With regard to documentation: do you mean the om-next-fullstack readme?

levitanong12:09:56

Sure thing 🙂

anmonteiro13:09:54

merged, thanks

levitanong13:09:13

@anmonteiro: another thing, I'm thinking this should also be documented in the om.next docs. I foresee a lot of boot users running into this.

levitanong13:09:23

What say you?

levitanong13:09:18

Maybe it can be an entry in the FAQ, until enough oddities appear to warrant an oddities page. :p

anmonteiro13:09:43

@levitanong should definitely go in the FAQ IMHO

dankweaver16:09:47

{:todo/list [:db/id :todo/editing :todo/completed :todo/title]} <- taking an example from the todo mvc

dankweaver17:09:12

does OmNext have any prescriptions for later issuing a query that wants the following information:

dankweaver17:09:33

{:todo/list [:db/id :todo/editing :todo/completed :todo/title :todo/time-created]}

dankweaver17:09:16

{:todo/list [:db/id :todo/time-created]} should be sufficient information, so ideally you would avoid sending the entire query again right?