Hi,
I have a use-case where the component is given an id and it uses a generic
'reference-data' (e.g. :location/render) subscription to render. Is it possible
and idiomatic to do something like:
(register-sub
:location/render
(fn [db [id]] ))
(defn row
[{:keys [location-id]}]
Hi Daniel, yeah, at the moment I am subscribing to a map which 'row'
then keys into.
On a related note, I am actually moving this sort of logic out into a
subscriber so the component is really quite dumb and gets
{:location-desc s/Str} rather than {:location-id ..}. It simplifies
the components
Isomorphic means that the code works the same on the browser and the
server. So you write your code as a single SPA. On the browser that will
be rendered to a string and returned. In the browser you'll get the
fully rendered page and then your ClojureScript code will take over and
it will act as a
@Khalid check out
https://github.com/savaki/reagent-nodejs
It's 100% Node/JavaScript, no Nashorn and the majority of the code is used on
both server and client side. I opted to separate the small server/client stubs
into separate directories, but I suppose there's no reason it couldn't be
Double plus plus what @matthew said
M
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript group.
To unsubscribe from this group and stop receiving emails from
Unfortunately, Google's not the only search engine out there. And while they
are dominant, 2/3 of web searches go through them, why should I leave out the
remaining 1/3 because it's more technical challenging? Also, as vertical
search engines become more prominent, why would I want to make
I think maybe the easiest solution is to write simple luggable wrapper to bring
their own router. I would hate to have to bring in an entire framework like
rendr or not be able to use a library just because of my router choice.
M
--
Note that posts from new members are moderated - please be
Tristan,
I'm coming back to cljs and went initially for chestnut road.
I was with the impression that I needed repl inside vim.
That was not the case, When things seatle it ll be very nice.
But I found that vim clojurescript figwheel are awesome.
Here is my project.cjl
People have been asking about cljs.test usage for a while now. I've finally
written up some notes https://github.com/clojure/clojurescript/wiki/Testing.
Feel free to edit for clarity / typos etc.
David
--
Note that posts from new members are moderated - please be patient with your
first post.
Alex, doing a quick sweep of new public Vars in 1.7.0-RC1 that were not in
Clojure 1.6.0 (complete list of all 21 below), I noticed that the following
two do not have any doc strings. Intentional, or oversight?
*suppress-read*
Throwable-map
Andy
*suppress-read*
-Eduction
Throwable-map
cat
Airbnb'd Render has ClientRouter and BaseRouter both of which extend from
BaseRouter (link below)
https://github.com/rendrjs/rendr/blob/master/shared/base/router.js
I just looked it up and have not used this. I did use their battle tested
infinite scroll widget once and it was one of the least
Simple Generic Solution! vs complicated solution with special cases.
Obviously the former wins!
Thanks for the education Matt! ;)
Sent from my iPhone
On May 21, 2015, at 8:14 AM, Matt Ho matt...@gmail.com wrote:
Double plus plus what @matthew said
M
--
Note that posts from new
Clojure 1.7.0-RC1 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-RC1/
- Leiningen: [org.clojure/clojure 1.7.0-RC1]
The only change since 1.7.0-beta3 is CLJ-1706, which makes reader
conditional splicing an error at the top level (previously it
To eliminate the need to use 2 different routers, the only possibility I see is
to use a js library that works both on client and server-side. Backbone.js has
a minimal router like this, you may also want to check crossroads.js or
finch.js.
But something tells me that you'll need to write some
14 matches
Mail list logo
