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
The cause seems to be from this update to react-router-dom: c96c36a
The reason was that we relied on so-called "buggy behavior" of the router, and so we need to update to react-router-dom v6.20.1 and/or figure out the correct way of referencing things relative to the parent page, not the current page: remix-run/react-router#11052 (comment)
Fix navigation Update to v6.20.1
Add end-to-end test
According to the React Router issue I linked to above, the authors of React Router will release a statement with explanations about how to migrate to the new behavior.
The text was updated successfully, but these errors were encountered:
The tabs somehow are trying to navigate relative to the current URL and not the transaction URL, so if you click the Trace tab enough times, you get
/tx/0xaf226ef77eae07429d123f3779ec747580dcf1b621014acf9085fcb426a783b0/trace/trace/trace/trace/trace/trace/trace/trace/trace/trace
The cause seems to be from this update to react-router-dom: c96c36a
The reason was that we relied on so-called "buggy behavior" of the router, and so we need to update to react-router-dom v6.20.1 and/or figure out the correct way of referencing things relative to the parent page, not the current page: remix-run/react-router#11052 (comment)
Fix navigationUpdate to v6.20.1According to the React Router issue I linked to above, the authors of React Router will release a statement with explanations about how to migrate to the new behavior.
The text was updated successfully, but these errors were encountered: