...then it is unable to navigate back if you are for example on the Login page.
The URL in the address bar is still being updated, but I assume it cannot track the view.
Wrapping the match statement in a view, like it is shown in the book, properly tracks the router again.
While this is shown in the book example it is still quite error prone.
One way this might be fixed is by making Router always wrap its closure in an implicit view.
Unless there's some restriction with the reactive system that I'm not aware of.
To Reproduce
Create an app with a router like in the code snippet above.
Attempt to navigate by using the navigate() function.
Get stuck on the current rendered component.
Expected behavior
Navigate to the url when using navigate().
Describe the bug If a router is created like this...
...then it is unable to
navigate
back if you are for example on theLogin
page. The URL in the address bar is still being updated, but I assume it cannot track the view. Wrapping the match statement in a view, like it is shown in the book, properly tracks the router again.While this is shown in the book example it is still quite error prone. One way this might be fixed is by making
Router
always wrap its closure in an implicit view. Unless there's some restriction with the reactive system that I'm not aware of.To Reproduce
navigate()
function.Expected behavior Navigate to the url when using
navigate()
.Environment