Rooba
/
mitmproxy
mirror of https://github.com/mitmproxy/mitmproxy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[web] use props.location instead of context.location

This commit is contained in:
Jason 2016-05-24 23:16:30 +08:00
parent 61453aa847
commit 6bf74955b9
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
web/src/js/components/proxyapp.js
View File

@ -28,14 +28,13 @@ var ProxyAppMain = React.createClass({
location: React.PropTypes.object.isRequired,
},
contextTypes: {
location: React.PropTypes.object,
router: React.PropTypes.object.isRequired
},
updateLocation: function (pathname, queryUpdate) {
if (pathname === undefined) {
pathname = this.context.location.pathname;
pathname = this.props.location.pathname;
}
var query = this.context.location.query;
var query = this.props.location.query;
if (queryUpdate !== undefined) {
for (var i in queryUpdate) {
if (queryUpdate.hasOwnProperty(i)) {
@ -48,7 +47,7 @@ var ProxyAppMain = React.createClass({
getQuery: function () {
// For whatever reason, react-router always returns the same object, which makes comparing
// the current props with nextProps impossible. As a workaround, we just clone the query object.
return _.clone(this.context.location.query);
return _.clone(this.props.location.query);
},
componentDidMount: function () {
this.focus();