This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
Property route undefined on replacement of route #27
Labels
Comments
georgberecz
changed the title
Route undefined on replacement of route
Property route undefined on replacement of route
Jul 3, 2017
Hello @georgberecz , |
Wasn't it fixed by #25? |
Hi @georgberecz! Did you give a shot to the new ß3? Feel free to keep us update about your issue :) |
Closing due to inactivity |
Thanks @georgberecz This actually worked I was getting the same error when using history.replace("...") the second time. It works the first time though. |
@insaneinc01 Do you have an example (or a Github) repo that reproduces the issue? |
This should be fixed in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey Leo,
thanks for looking into #23 and updating the Renderer. The rendering of multiple cards is not a problem anymore. However, there is now an error inside the NavBar:
I'm using the newest release candidate:
"react-router-navigation": "^1.0.0-rc.2",
I looked into the code and I think I've found something. In the DefaultRenderer replacing
return [ ...acc.slice(0,indexOf), scene ]
with
return [...acc]
and therefore, using the last occurrence in case of finding a duplicate index fixed it for me. With the old code the newly replaced route was simply sliced of again and replaced by the old one. However, the
scene
in theownProps
was still the new one, but could not be found in the newly generatedscenes
, which resulted in the exception.Thanks for looking into that and keep up the good work,
Georg
The text was updated successfully, but these errors were encountered: