A Simple Way to Route with Redux
jlongster.com
A Simple Way to Route with Redux
1–10 of 57 posts
Re: A Simple Way to Route with Redux
#2[deleted]
Re: A Simple Way to Route with Redux
#3It's disappointing that this depends on React's router, considering Redux is an agnostic framework. Unless I'm reading something wrong here..
Re: A Simple Way to Route with Redux
#4I recently switched to this library from Redux Router for a project, after having trouble with server-side routing.
It really is simple, as stated in his title, and I would definitely recommend it if anyone is using Redux and React Router.
Re: A Simple Way to Route with Redux
#5It's disappointing that this depends on React's router, considering Redux is an agnostic framework. Unless I'm reading something wrong here..
Purpose of this library is to be able to use react-router with Redux, that's what the dependency comes from.
Re: A Simple Way to Route with Redux
#6It's disappointing that this depends on React's router, considering Redux is an agnostic framework. Unless I'm reading something wrong here..
Purpose of this library is to be able to use react-router with Redux, that's what the dependency comes from.
I understand that, and it's disappointing. I was excited about the prospect of a very lightweight router to use with Redux that didn't require React as a dependency. Oh well, I guess that's why Github has a "fork" button :)
Re: A Simple Way to Route with Redux
#7Earlier quoted context omitted.
Purpose of this library is to be able to use react-router with Redux, that's what the dependency comes from.
I understand that, and it's disappointing. I was excited about the prospect of a very lightweight router to use with Redux that didn't require React as a dependency. Oh well, I guess that's why Github has a "fork" button :)
What are you using if not React? Why wouldn't you use React if you are using Redux?
Re: A Simple Way to Route with Redux
#8It's disappointing that this depends on React's router, considering Redux is an agnostic framework. Unless I'm reading something wrong here..
From the post:
> After integrating redux and react-router in my site, I extracted my solution to a new project: redux-simple-router. The goal is simple: let react-router do all the work. They have already developed very elegant APIs for implementing routing components, and you should just use them.
The explicit goal of the project is to take advantage of react-router's existing tools when used with redux, it doesn't make any sense to lament that it depends on react-router.
Re: A Simple Way to Route with Redux
#9It's disappointing that this depends on React's router, considering Redux is an agnostic framework. Unless I'm reading something wrong here..
A slightly tangential question.
What is the benefit of using react-router (I am assuming on the client side) versus using a server side router that comes with whatever web framework that you are using?
Re: A Simple Way to Route with Redux
#10I recently switched to this library from Redux Router for a project, after having trouble with server-side routing. It really is simple, as stated in his title, and I would definitely recommend it if anyone is using Redux and React Router.
I've been struggling with redux-router all week, and was just about to spend today trying to switch to this project. Glad to hear your experience. :)