v0.4.0-alpha.3 breaks @connectSee original GitHub issue
We recently updated to the latest version of found to be able to use the latest
react-redux version. Everything works fine until we try to use
@connect in our component.
@connect is used on a component passed to the
Route, it produces the following error:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.
We narrowed this down to be caused by the
context prop being passed by
found, which has the value of the
matchContext. If the
context prop is removed/renamed before the
@connect call, everything works as expected.
react-redux changelog, there is a mention of this change, but I’m not sure as to how fix it properly.
Maybe we should pass the
matchContext with a different prop name to avoid any possible collisions?
- Created 4 years ago
- Comments:8 (8 by maintainers)