I am noting the following in the compiled JS output when using optimizations
:none
goog.provide('simple_test.core');
goog.require('cljs.core');
goog.require('simple_test.beta');
goog.require('clojure.string');
goog.require('clojure.string');
goog.require('simple_test.beta');
I noticed this a while back [1]. I ended up not caring anymore since it doesn't
hurt and is removed by :advanced anyways.
FWIW it is caused by the alias (:require [clojure.string :as str]) which ends
with goog.require for 'clojure.string and 'str (which resolves to
'clojure.string). Without an
On Sunday, December 14, 2014 6:56:28 AM UTC-5, Boris Kourtoukov wrote:
On Sunday, December 14, 2014 6:53:53 AM UTC-5, Thomas Heller wrote:
I noticed this a while back [1]. I ended up not caring anymore since it
doesn't hurt and is removed by :advanced anyways.
FWIW it is caused by the
This is really cool. I'd been bringing in D3 just to use scales and other math;
I think bardo obviates that, which is great from a payload standpoint.
Slightly off-topic, sorry, but what's the story with all the tests being
commented out, just out of curiosity?
--
Note that posts from new
Generally I think you'd have each table row connected to a reagent.core/atom
(or, alternately, a part thereof); then you would just need to attach the
checkbox on-change handler to a swap! function that modifies the state
accordingly.
Inspecting state is then just a question of the atom being
Thanks for the info. Sablono goes a long way, but yeah, you still have
om/build.
On 14 Dec 2014 14:32, pande...@gmail.com wrote:
Just adding to the description of API differences: with reagent one is
able to use clojure's (for ...) to iteratively generate subcomponents,
without the need for an
I was mostly doing repl testing. I had a few tests but when you're trying to
test composition of a number of transformation functions it becomes pretty
impossible to write well formed tests. Next on my list is adding some more
robust tests using https://github.com/cemerick/double-check
On
Yeah I can imagine it isn't easy to test that stuff well. (So it wasn't
directly cljx/cljs related, which was my interest.)
Thanks for the report.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are
This is great! Thanks for sharing. Looks really flexible. I'm looking
forward to replacing my own sightly buggy easing functions with this. :)
On Sun, 14 Dec 2014 17:47 null pande...@gmail.com wrote:
Yeah I can imagine it isn't easy to test that stuff well. (So it wasn't
directly cljx/cljs
There's a nice example of how to do this here:
http://yogthos.net/posts/2014-07-15-Building-Single-Page-Apps-with-Reagent.html
About.halfway through the article, he implements a multi-select list component,
which is basically the pattern you are looking for.
--
Note that posts from new
10 matches
Mail list logo
