@bhauman: trying to figure out integrate reconcilers into the existing devcards model

it seems you use React for the whole page so you control the root

this is not actually a big problem for Om Next, things are decoupled enough that a reconciler doesn’t really need a real root to work

but I’m struggling a bit with the custom card w/ state example

the init-state bit can I pass my own atom here instead of plain data?

@dnolen: yes you can

@bhauman: and what is the state filter bit for (the second argument)?

@dnolen: where are you?

oh custom card with state

state-over-time-view in custom_cards.cljs example

basically want to sort this out so I can start writing real UI tests for Om Next

and then of course doc that so everyone else can too

@dnolen: if I am understanding you correctly (fn [state _] _ is the react element owner. but still not sure if that is what you want

@dnolen: happy to chat if that helps

ok I was just curious, yeah I don’t need the parent element

@bhauman: so every time the state changes this fn will be invoked?

and I should return a new component?

@dnolen the function will be invoked, you need to return a react element

ok so that’s actually a bit of problem

since Om Next is incremental it finds components to update

thats fin

thats fine

and avoids starting at the root

so if you want to update internally thats no problem

so just don’t give state param?

exactly

just create a react container that works for your

purpose

@dnolen: actually the devcard option :watch-atom false should prevent rerenders of the function, verifying that right now

@dnolen: but I was thinking that I/we would be writing a defcard-next to handle the history and data display bits

yes that would be the next step

I just want to get basic rendering without a real root working first

@bhauman one thing I don’t understand is how to pass options

like :watch-atom false

is it just with the last map argument?

@dnolen yep with that last options map

:watch-atom false doesn't work

sorry, it's a bit complicated

@dnolen: ^

ah k

but I can just return a component and be done with it right?

yep

@dnolen: I'm anxious to help so if you have any problems or if you think making :watch-atom false work will help. Let me know

nah

I just want the most basic thing to work

and then would like to explore how to reuse or reproduce the state functionality you already have

MIND BLOWN

https://github.com/omcljs/om/commit/c0963bbe97e959a6a7408dadf5bb7612df419993

the only changes that were required are in the second file

that’s all Om Next needed to be fully mocked into an existing React component tree

heck yeah!!

(defcard test-counters (om/mock-root counters-reconciler CountersApp))

that’s it

That's awesome!!

@bhauman: so yeah the only thing I would want is the ability to give you a history hook

but have that only get fired when history controls are used

re-render should never fire

OMFG this is going to save me so much time

@bhauman: so can devcards display an atom?

@dnolen yep!

@bhauman: hrm how?

if I have my component as the first thing and try to return my atom as the second thing - that doesn’t work

@dnolen: to display an atom its (defcard my-atom atom-reference)

@bhauman: so there’s no standard mechanism for showing different card types in one card?

@dnolen: if I understand you correctly yes

but it's definitely been on my mind

you could of course compose via react

@bhauman: but you can’t nest cards right?

@dnolen: nope

not obviously

got it, can live with that

React is awesome

I'm looking for clarity about how to replace both in the new version of prismatic schema. (`both` is now deprecated) I want to assert that something is BOTH a sorted-map and that the key/value pairs of the sorted-map are of certain types. My previous, working schema was this (notice use of both):

(def schema  {:a  (s/both
                   PersistentTreeMap   ;; is a sorted-map (not just a map)
                   {TODO-ID TODO})     ;; in this map, each todo is keyed by its :id})

(def schema  {:a  (s/constrained
                   PersistentTreeMap   ;; is a sorted-map (not just a map)
                   {TODO-ID TODO})     ;; in this map, each todo is keyed by its :id})

Okay, the penny has dropped. (s/both a b) can be written as (s/condition a b) ... the a is checked as the predicate and b is checked as the body. Sneaky. So the final solution was: (s/condition #(instance? PersistentTreeMap %) {TODO-ID TODO})

How would I go about requiring something to be an instance of goog.date.UtcDateTime using Prismatic Schema?

Who’s compiling to Node.js? Please chime in here if you could be affected by a change in how the shim finds required files: http://dev.clojure.org/jira/browse/CLJS-1444

@martinklepsch: For anybody interested in node.js the other ticket to look at (and patch to try) is http://dev.clojure.org/jira/browse/CLJS-1466

@joelkuiper: @dnolen @richiardiandrea re: cycle.js After talking to the author (great guy!) about the library I got the impression that there is a lot of Not Invented Here in his work. There are some interesting ideas to extract (the specific RxJS + VDOM combination) but I wouldn't recommend it as it is, since it ignores the existing ecosystem and pretends to be a standalone final solution...

@bensu oh, nice. missed your last comment there.

@bensu ReactiveConf looked like an interesting event from afar.

Hi there. I only have a basic understanding of clojurescript, but I’m fairly comfortable with javascript, and I was hoping I could ask for some pointers on what the equivalent cljs ought to look like, because I couldn’t see an example on this site: http://himera.herokuapp.com/synonym.html

If I want to use an existing js library, like http://momentjs.com, and call moment().format('L'); what would the equivalent clojurescript look like? Something like ( js/moment ( js/format ‘L’) ) ?

@mikethompson: That penny kept falling through to me as well - time to finally get rid of those pesky deprecation errors

(.format (js/moment.) “L”)

delaguardo: thanks! So as long as that js file is included on the page and loaded before clojurescript’s compiled javascript, I should be able to call it freely?

Yes, but there is more native way for external libraries - http://lukevanderhart.com/2011/09/30/using-javascript-and-clojurescript.html

cool - looking up now

@delaguardo: that should be (.format (js/moment) “L”) I think

mrchrisadams:

oh, my bad, but

moment()

new moment()

Anyone here build an electron/clojurescript app? Seems like it should be fairly easy but just moving the proper js files into the electron shell. Are there any gotchas or tips to improve the workflow?

@jstew quite few people doing that far as I can tell

@dnolen can you elaborate on "fwiw I think core.async + React / Figwheel has shown that mutable observation is a big tradeoff" re:cycle.js? Or point to any resource explaining it? not quite following.

@acidandy: if you haven’t tried it then it will be difficult to understand

but mutable observation is a resource and must be managed if you need a life cycle

which you do in the React model esp. if you want stronger state management (time travel)

similar for hot code loading, you need to be very careful with observation

basically the observe operation is fundamentally stateful

Ah I see. Wasn't sure if it related to observers in that sense. Thanks!

the issue becomes clearer when you see that React events don’t need explicit addEventListener or explicit removeEventListener

this is a huge source of complexity that React just removes

you see the exact same problem found around traditional JS event handlers in RxJS observe/unobserve and in core.async loops that need a lifetime

not sure if this is more of a cider question vs clojurescript, but since I’m working in a cljs repl: can anyone give me a pointer on how to get my repl values to be pretty printed? I’m using whidbey for colorizing, but can they also be nicely broken into indented lines?

as opposed to, for example:

cljs.user> {:a {:b {:c :d} } }
{:a {:b {:c :d}}}

@bhauman: there’s not a version of devcards w/ React 0.14 is there?

Not yet.

@dnolen: ^

k

@bhauman: I'm trying to start with figwheel 0.5.0 and it complains that Could not locate clojurescript_build/auto__init.class or clojurescript_build/auto.clj on classpath. I looked through figwheel's project.clj and it's not there

should it be there?

oh, that's in my project, heh

forgot to remove it

I'm starting figwheel sidecar from a clojure.main REPL. Everything works fine except (reload-config): java.lang.IllegalStateException: Can't change/establish root binding of: autobuild-env with set

Am I missing something in my config/is there a known fix? My friend Google isn't helping

Oh wait...figwheel didn't load the config, I did. Duh. Nvm.

Can’t figure out how to generate URLs on cljs frontend using shared cljc file with silk routes pointing to backend clj handler functions.

@domkm: ^ can you maybe help me again?

@pshk4r: Could you make a gist of what you have so far?

@domkm: well, it’s pretty stupid now: https://gist.github.com/vitaly-pushkar/7e3715c8cc99388cbec6 of course cljs cannot ’see' clj handlers, but I actually don’t need it - what I want is to ask silk to give me urls for named routes, to not to hardcore urls on frontend and I can’t figure out how to make it possible

@pshk4r: Have you tried silk/depart or silk/unmatch?

@domkm I can’t run the app. I get adzerk.boot_cljs.util.proxy$clojure.lang.ExceptionInfo$ff19274a: No such namespace: me.front-office.handlers, could not locate me/front_office/handlers.cljs, me/front_office/handlers.cljc, or Closure namespace "me.front-office.handlers” - it tries to load my clj handlers as cljs which doesn’t exist, obviously

@pshk4r: You'll need to use reader conditionals #?(:clj ... :cljs ...) to conditionally load code that is only compatible with one environment

@pshk4r: Though that's a general issue, I don't yet really understand what you are trying to do with Silk

@domkm, Let me try to rephrase it: I want to have one shared place between frontend (with cljs Reagent) and backend to define routes in. So whenever I need a link on frontend to point to pages which are not part of SPA (for example, /registration or /about ), I could use named routes instead of hardcoding these urls. I am pretty newbie here, maybe I get the whole thing wrong and trying to do something illogical.

@pshk4r: Use reader conditionals to exclude serve stuff from CLJS routes

@pshk4r: Here's a good primer on reader conditionals: http://danielcompton.net/2015/06/10/clojure-reader-conditionals-by-example

@domkm: I will try, thank you a lot.

sure thing