Router not executed on page changes about perseus HOT 7 CLOSED

Now that that PR has been merged, there are a few minor changes that need to take place for this to work with regards to setting global variables.

from perseus.

Okay, fixing this seems to be just about impossible until we can get the user's Routes into the RouteVerdict enum somehow. Right now, that's done with context, which doesn't work because it's not in a reactive scope, and global variables can't be used because they need to be generated in the CLI subcrates with macros. If the Route trait's method match_route took &self as a parameter, this would enable the very efficient solving of just about all these problems, which I've proposed here. Until there's some action there, this likely won't go anywhere. Any other solutions would be greatly appreciated!

from perseus.

With #12 dealt with, this is now a single problem in the router, as a verdict is successfully generated, but for some reason Sycamore then doesn't run the logic to match that verdict and actually render a new page. This results in no exceptions and no identifiable error messages.

from perseus.

With #2 closed and major changes to the app shell, this bug is now manifested in its third iteration: locale detection will call Sycamore's navigate function, which causes a blank screen, and all other routes are treated as external and reload the entire page. Neither of these behaviors are desirable, but the first priority should now be to have all routes treated as internal and thus to simplify this down to one problem of router execution, as it was in its previous version.

from perseus.

Okay, the new issue of not intercepting click events seems to be caused by the fact that the Sycamore router only handles click events for its children, and Perseus simply renders an empty template, hydrating to an element that the router doesn't control. I'll work on a fix for this now, and see what happens to the other part of this bug.

from perseus.

Okay, we are back to one bug! Links now behave correctly as in an SPA, and now it's just that the closure passed to Router is never properly called.

from perseus.

Thank you @lukechu10 for all your help on this one! Greatly appreciated!

from perseus.