Unknown prop `staticContext`

It looks like the recent change to add staticContext to the prop types has the unintended consequence of passing undefined outside of StaticRouter.

const MyCmp = withRouter(function({ match, location, history, children, ...props }) {
  return <div {...props}></div>;
});

I’m not 100% of my diagnosis but it seems close, any ideas?

[matthewrobb]

It may be that people will need to adjust to filter out staticContext but it introduced a bug for me where my assumption was that the only props is be getting from withRouter were match location and history. So that assumption falls over when I want to pass every other prop on to a regular Dom element. I’m now inadvertantly passing an undefined staticContext prop.

Yes I can and now am filtering it out but its existence was unexpected since I’m not using a static router.

[matthewrobb]

Is there no way to omit the prop from being passed when not in a static router? It seems like an edge detail that most users will have to guard against without having any idea why. If it’s only on the passed in context/props when present the end result for the guards stays the same and destructured {staticContext} will remain undefined. The only difference is that object rest will not pick it up. Maybe the problem lies there. I almost feel like Object Rest shouldn’t bring over undefined properties at all.