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
I read the issue that history is separated from its own context (#7103).
From the result of that, __RouterContext doesn't be exported from v5.2.0 react-rotuer-dom? @_@
Acutally, I have used __RouterContext for making own custom hooks because there not exists hooks before 5.1.0 @@... from this update(5.2.0), that does not export __RouterContext @@...now I have to refactor all my code If I want to use latest vesion
The text was updated successfully, but these errors were encountered:
@timdorr yes you have, react-router-dom used to export * from 'react-router', then it was changed to only export some things explicitly here: e951e1d. That change caused __RouterContext to no longer be exported.
I know it's not public API, but the current sad state of affairs is that the convenience of making our own hooks to get stuff from __RouterContext outweighs the inevitable disruption of using non-public API. There's a serious need for making the context officially supported API or adding a public hooks API.
I read the issue that history is separated from its own context (#7103).
From the result of that,
__RouterContext
doesn't be exported from v5.2.0 react-rotuer-dom? @_@Acutally, I have used
__RouterContext
for making own custom hooks because there not exists hooks before 5.1.0 @@... from this update(5.2.0), that does not export__RouterContext
@@...now I have to refactor all my code If I want to use latest vesionThe text was updated successfully, but these errors were encountered: