What is the trade off between history push and replace?

reactjs react-router browser-history
Kris MP picture Kris MP · Sep 6, 2016 · Viewed 26.1k times · Source

I use History package to redirect invalid URL to 404 page on my react component.

I use .replace instead of .push simply because I don't want the browser to record any invalid url I have visited.

Have I missed the point here? And is there a trade-off between choosing one or the other for my purpose?

Can someone explain to me? thanks in advance ;)

Answer

vgrafe picture vgrafe · Sep 6, 2016

I think you have the right idea.

I personally use .replace when redirecting from an invalid url (or non relevant, i.e. redirect to "profile" page when a logged user goes to the "/login" url), so using the browser's "back" button works properly for the end user.

Related questions

How do i pass state through React_router?

Here is the file that's causing me trouble: var Routers = React.createClass({ getInitialState: function(){ return{ userName: "", relatives: [] } }, userLoggedIn: function(userName, relatives){ this.setState({ userName: userName, relatives: relatives, }) }, render: function() { return ( <Router history={browserHistory}> <Route path="/" userLoggedIn={this.…

Read More
Component is not getting rendered after history.push()

On a button click, I am getting the URL changed by doing history.push() import createHistory from 'history/createBrowserHistory' const history = createHistory() . . some code . history.push(`/share/${objectId}`) and hoping the component mentioned in the Route for that URL would …

Read More
Gatsby.js: Navigating with URL Parameters and the Browser Back / Forward Buttons

I have an Articles component which displays a list of posts. The list is paginated so that a maximum of 10 posts can display per page. There is a "Next Page" button that when clicked will update the component state and …

Read More