Hi James,
If I understand your pattern correctly, you assoc a :routes entry to each
component that contains routes. Then your router component depends on these
components, selecting those that have a :routes key, and call each :routes
value function in turn until one return a non-nil Ring respo
On 8 January 2015 at 15:10, Malcolm Sparks wrote:
>
> The idea here is that you want individual components to be able to
> 'contribute' groups of routes. That way, you can avoid the common practice
> of having one big 'god' namespace containing all the Ring routes, which is
> then tightly coupled
Hi James,
Yes. The idea here is that you want individual components to be able to
'contribute' groups of routes. That way, you can avoid the common practice
of having one big 'god' namespace containing all the Ring routes, which is
then tightly coupled to all your Ring handlers. Instead, it's nice
Out of curiosity, does Modular have a mechanism for abstracting groups of
Ring routes?
I'm wondering how much work can be shared between Modular and other
projects, such as my own Duct template, which has similar ideas.
- James
On 8 January 2015 at 14:42, Malcolm Sparks wrote:
> I've created a
Awesome, thank you!
2015-01-08 15:42 GMT+01:00 Malcolm Sparks :
> I've created a new website to help new Clojure developers get started with
> Clojure and specifically with Stuart Sierra's component/reloaded-workflow
> pattern.
>
> On http://modularity.org you can find documentation about modular
I've created a new website to help new Clojure developers get started with
Clojure and specifically with Stuart Sierra's component/reloaded-workflow
pattern.
On http://modularity.org you can find documentation about modular. Modular
comprises :-
- a set of pre-written components
- a template
