Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ghedamat/reagent-react-router

A simple experiment to use react-router with reagent and clojurescript
https://github.com/ghedamat/reagent-react-router

Last synced: 22 days ago
JSON representation

A simple experiment to use react-router with reagent and clojurescript

Awesome Lists containing this project

README 

        
# Reagent-React-Router



A simple experiment on how to use [react-router](https://github.com/rackt/react-router) in clojurscript and [reagent](https://github.com/reagent-project/reagent)



## Current Status



very very alpha



## Disclamer



My understanding of clojure/clojurescript is quite limited, looking for suggestions and improvements is the main reason for this repo to exist.



## How it works



All the code is in `src/reagent_react_router/core.cljs`.



React-router has a very simple api that allows you to define routes as a nested series of components [docs](https://github.com/rackt/react-router/blob/master/docs/guides/overview.md#with-react-router).



The outer component is then passed to the `run` function and by means of passing a callback we can determine where to render on the page.



This project is simply wrapping the `Link` and `RouteHandler` components provided by react-router to use them in reagent components via the amazing `adapt-react-class` api that reagent provides.



Route definition is a bit trickier because reagent's `reactify-component` wraps the component in a `` and that can't work (currently) with react-router.



The current implementation provides a `Route` and a `DefaultRoute` function to be used in the route definition process.



example:



```clojure

  (def routes

    (Route {:name "app" :path "/" :handler app-page}

      (Route {:name "about" :path "about" :handler about-page}

        (Route {:name "nested" :path ":post_id" :handler nested-page}

          (Route {:name "deeply-nested" :path ":comment_id" :handler deeply-nested-page})))

      (DefaultRoute {:handler default-page-meta})))



  ;; or



  (defroutes [:route "/" app-page

              [:route "about" about-page

               [:route ":post_id" nested-page

                [:route ":comment_id" deeply-nested-page]]]

              [:redirect "red" "about"]

              [:not-found not-found-page]

              [:default-route default-page-meta]]))



```



Finally a `run-router` function is provided to boot up the app



```clojure

(defn init! []

  (run-router document.body routes))

```



### A note on dynamic segments



React-router has excellent support for [dynamic segments](https://github.com/rackt/react-router/blob/master/docs/guides/overview.md#with-react-router), normally they're used by including a mixing in the react-component that needs them BUT there's also an option that allows passing them down from the topmost component.



That's what is begin done for now.

any reagent component nested under the route will receive a `params` jsObject, every time a `RouteHandler` is defined, the map should be passed as its argument so that is available to the nested components.



The params in the jsObject are accessed as any other jsObject in clojurescript.



Note that if params are used in a component and the params object changes the component tree will be rerendered from there downwards. This is probably something that could be made more efficent...



## Whishlist/TODO



`defroutes` is being added to have a more reagent-like api, still has some quirks.



I haven't used this in any real apps yet so it's quite likely that some of the use cases covered by the router are missing/won't work properly.



* Query params support hasn't been tested at all



# Feedback



Please let me know what you think, if this makes sense at all and how it could be improved!