Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
v0.4.0-alpha.3 breaks @connect
See original GitHub issueHi!
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.
If @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.
In the 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?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
okay, released in the latest alphas of found (and found-relay as appropriate)
it’s actually already on the
matchprop. we’re just passing it in twice. will address