Jürgen Wenzel
Jürgen Wenzel
# 💬 RFC This document describes how the routing in Aurelia v2 differs from the routing in v1 (and other frameworks which uses a url-based routing). If you're new to...
- [x] Compositional routing - [x] Navigation instructions, `NavigationInstruction` and `ViewportInstruction` - [x] Navigating with `goto` and `a`nchor links - [x] No route configuration needed - [x] Manually configure v1...
# 💬 RFC In addition to the "traditional url/path configured routing" the new router will have a viewport centric routing based on conventions. This RFC contains an early version of...
# 💬 RFC Looking for sounding boards/opinions to something long and not so structured: how relative links find the right scope to search for viewports. It'll help if you understand...
# Pull Request ## 📖 Description This PR fixes issues that could occur when several denying async router hooks were applied to the same component. ## 📑 Test Plan -...
…in IE/Edge Necessary for PR aurelia/router/history-state-consolidation
Preventing a navigation with canDeactivate doesn't cancel the browser history navigation. This fix moves the browser back to the index where navigation was cancelled. Depending on PR aurelia/history-browser#42. Closes aurelia/router#528.
Adds stateful routes so that route configurations can specify a module or a module in a viewport as `stateful: true`. A stateful module that's loaded in a viewport is never...
I've got code for stateful routes, meaning that if you do this ``` { route: 'dashboard', name: 'dashboard', viewPorts: { 'default': { moduleId: 'dashboard', stateful: true } } } ```...
Adds a `params` parameter to the `navigate()` function, so that ``` router.navigate('#/main/:id/details', undefined, { id: 123, name: "onetwothree" }) ``` results in navigation to ``` '#/main/123/details?name=onetwothree' ``` In other words,...