#react-router

Guess what everyone? I went missing for a month because its finally reached MVP status! All that work I did on that pretty frontend? Scrapped, it became boggy.

Now it looks ugly. This is because I learned that trying to deal with color too early results in slowing down and bike shedding

I ended up using deployd and react to actually get it done. I'm using superagent to make the restful calls. Everything is styled via style tags. And another project known as notebook.ai does everything it does and better, except for the map. And I learned this just after rushing through it to get it done in time for bookcon.

And you know what? I'm still proud of it. People have told me to be proud of it. People are giving me suggestions on how to improve it and make it different and better for my intended audiences.

When I come back to this project, I'm definitely converting the style tags to CSS in some way. I'm also probably going to swap deployd out for something that uses postgres instead of mongodb. I'm looking at expressa and liking what I'm seeing. I'm also probably going to work it so that more of the components use the mobx store instead of having five million random restful calls.

You can view the frontend code here . The tests are useless and fail due to how much I changed everything after trying to write my initial tests without thinking about how react-router works.

we will get to know about What is the Index route, dynamic routes with react-router, and nested dynamic routes.

In the previous article, we learned about nested routes with React routers. we have the products page which consists of two nested routes

featured which renders the list of featured products and

new which renders the list of new products

let's take a look at the nested routes to feature with react-router, so far we have seen how react-router helps us navigate across pages in our application.

But what you should know is that react-router also helps to switch between a portion of the view inside the page. If that is a little confusing, let me explain with a simple scenario.

Create and explore tech blogs on this platform.

Blogging platform where you can sign up and log in with username and password. See all blog posts. View user's profile page. Add, comment, like, sort, edit and delete posts. You can also filter by your favorite category.

Built with React, Redux and ES6. Routing is implemented with React Router.

Today, I spent couple of hours to fix the programmatic routing between components in react app.

When we specify route using “Route, BrowserHistory and Switch” components, we specify some routes as follows:

<BrowserRouter>

     <Switch>

         <Route path=“/signin” exact component={SignIn} />

    </Switch>

</BrowserRouter>

Here, my SignIn component renders when user clicks on signIn link. Above given route takes care of routing to SignIn component.

Problem Faced:

My SignIn component has child components “form and form-fields”. Actual, form submit ishappening in child component. On the success of submit, I was trying to route to another component from child component. This kept failing. 

Solution:

One of the major struggles that I’ve had since introduction of React to our ecosystem here at ExecOnline has been lack of testing routing on the client side. So this weekend I decide to sit down and solve this problem once and for all. 

Goal:

I have links sprinkled throughout the application created with react-router. User clicking on a link is transitioned to a different url and a different component is rendered. This works great in the browser, now I want to be able to test this behavior in a test

Solution:

Turns out that there are bit and pieces of information that I would need to extract from different places and it took me a few hours to figure out what those pieces are so I decided to collect it all in one place

I'm not sure how to have a fallback route?

<Route exact path="/dashboard" component={a.AdminHome} /> <Route path="/dashboard/responses/:id" component={a.Responses} /> <Route exact path="/dashboard/responses" render={() => <h3>Please go back and select a survey.</h3>} /> <Route path="/dashboard/bycard/:id" component={a.SurveysByCard} /> <Route exact path="/dashboard/bycard" render={() => <h3>Please go back and select a survey.</h3>} /> <Route path="/dashboard/groups/:id" component={a.SingleGroup} /> <Route exact path="/dashboard/groups" component={a.Groups} /> <Route path="/dashboard/subunits/:id" component={a.SingleSubunit} /> <Route exact path="/dashboard/subunits" component={a.Subunits} /> <Route path="/dashboard/idols/:id" component={a.SingleIdol} /> <Route exact path="/dashboard/idols" component={a.Idols} /> <Route path="/dashboard/cards/:id" component={a.SingleCard} /> <Route exact path="/dashboard/cards" component={a.AllCards} /> <Route path="/dashboard/survey/:id" component={a.SurveyView} /> <Route exact path="/dashboard/survey" component={a.NewSurvey} />

react-router로 router 기능을 사용하여 개발 시 아래와 같인 경고를 console에서 볼 때가 있다. 그렇다면 아래와 같이 해결하면 된자.

Warning: [react-router] `Router` no longer defaults the history prop to hash history. Please use the `hashHistory` singleton instead.

해결 방법은 아래의 코드를 확인하자

// 변경 전 render(( <Router> <Route> ... </Route> </Router> ),document.getElementById('root')) // 변경 후 import {hashHistory} from 'react-router' ... render(( <Router history={hashHistory}> <Route> ... </Route> </Router> ),document.getElementById('root'))