Search Hashnode

Search posts, tags, users, and pages

Comment by Kenan on "React Tutorial using MERN stack" | Hashnode

Discussion

Popular posts

CommentReact Tutorial using MERN stack

Kenan

Feb 5, 2016

I'm having problems adding priority and status query to url. When I use this.props.history.push, like you did, I get a warning that it's deprecated.

But when I use browserHistory.push({search:'?' + $.param(filter)}), I get url that looks like this localhost and it doesn't get recognized by this.props.location.

Kenan

Feb 5, 2016

Also, why is cursor.next() used? Why should we return next document instead of the current one?

this.props.history is deprecated, because in history 2.0 the right way to do it is using this.props.router. If you use browserHistory, you are setting the URL's search path, not the search part of the hash. If you don't like this.props.history, then try hashHistory instead of browserHistory, that'll work because it will set the hash part correctly. Alternatively, read up on Histories and try using browserHistory instead of hashHistory (which is the default) in the router.

Vasan Subramanian

Previous generation techie

Feb 8, 2016

Vasan Subramanian

Previous generation techie

Feb 8, 2016

find() returns a cursor, and the only way to get to the first document is by calling next() on it. There is no 'current' document. We could have used the deprecated findOne() instead, which returns the first document directly.

Kenan

Feb 10, 2016

Thank you, I've managed to get it working. I'm using hashHistory and 'this.context.router.push'. I've switched to ES6 classes in the process, I don't know if that was necessary. Here's my code for BugList component if anyone needs it. https://jsbin.com/wuvexa/edit?js