You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when subsequent external data changes, and I call React.renderComponent again with a new value for myProps, the MyApp only ever receives the very first myProps value, and never any updated value (debugged in MyApp#componentWillReceiveProps()). I am not sure why the value would not get passed through the router, but I can't find any other explanation after several hours of debugging.
The text was updated successfully, but these errors were encountered:
tl;dr: we will give you a chance to determine the props for a route before we activate it. Its not the same as just rendering <Routes/> over and over, but I think it meets the same use-case.
Have a read through that stuff, if it doesn't look like it helps, please make some noise and I'll reopen this.
For now, you'll need some way to subscribe to that those data changes in your handlers to get the new data.
I have the
<Routes>
component as my top-level React component. It has a custom child property, like this:However, when subsequent external data changes, and I call
React.renderComponent
again with a new value formyProps
, theMyApp
only ever receives the very firstmyProps
value, and never any updated value (debugged inMyApp#componentWillReceiveProps()
). I am not sure why the value would not get passed through the router, but I can't find any other explanation after several hours of debugging.The text was updated successfully, but these errors were encountered: