Fork me on GitHub
#untangled
<
2016-03-23
>
folcon16:03:13

@tony.kay: Did the untangled tutorial drop mentions to :keyfn in the UI exercises? I remember needing to add it to the person component, or am I mis-remembering?

tony.kay16:03:36

you need it, but at the UI chapter, you don't know enough to write it

tony.kay16:03:40

since there are not queries

tony.kay16:03:56

If it is missing in the later chapter on UI/queries, then it needs to be added

folcon16:03:22

ok, I’ll keep an eye out for that

folcon16:03:50

@tony.kay: Ok, I found one very confusing thing. For some reason (enable-console-print!) is not called inside the untangled_tutorial.B_UI_Exercises. This means that click events such as the input :onClick (fn [e] (println "TODO ex 3")) aren’t instructive as they never print to console...

abtv17:03:59

@tony.kay: what is the best way to start new (pet) project using untangled framework? just clone todo app? or maybe there is some template for it? I need both client and server

tony.kay17:03:58

@abtv: Todomvc is the best template for now

tony.kay17:03:38

@folcon: PR welcome! Otherwise, I'll try to remember it...very busy 😉

folcon23:03:17

hmm, ok, in E-UI-Queries-and-State-Exercises, I have no idea how to do recursive access of :person/mate without stack overflow. So far the best I’ve got is:

static om/IQuery
  (query [this] '[:db/id :person/name {:person/mate [:db/id :person/name]}])
Just doing:
static om/IQuery
  (query [this] `[:db/id :person/name {:person/mate ~(om/get-query Person)}])
Blows up...