Router Recipes
While the docs do a great job explaining the intricacies of the router, sometimes you just need a code snippet and a brief explanation to do something. You will find code snippets for basic things, from creating routes to working with router hooks.
Create a routeable component
A component that is loaded as part of a route definition. The IRouteableComponent
Getting the currently active route
When working with the router, sometimes you want to access the currently active route. The router provides an array of activeComponents
which can be one or more components currently active. In most instances, this array will only contain one component. However, if you are working with multiple viewports, this array will contain all components from those viewports.
By leveraging the route.match
property, we can get the currently active route. This is where you can access its data, path, name and other route configuration properties.
Get all registered routes
To get all registered routes, you can use the getRoutes
method from the rootScope
property of the router.
Creating a route
As outlined in the Creating Routes section, routes can be specified using the routes
decorator or the static routes
property.
Creating a route with parameters
A parameter is denoted by the prefixed colon :
followed by the parameter's name. In this example, our parameter is called productId
, which is required for the route to load.
You can have more than one parameter (as many as you like):
Creating a route with custom configuration values
Routes support a custom data
property allowing you to decorate your routes. Some use cases might include marking a route as requiring a user to be authenticated or an icon.
Creating a route with a custom viewport
Some routes might be loaded into specific viewports in applications with multiple viewports. You can use the viewport
property on routes to specify which route.
Loading data inside of a routeable component
Inside components displayed by routes, the best place is to load data inside canLoad
or load
hooks. If your view depends on the data being loaded (like a product detail page), use canLoad
otherwise, use load
. The first argument is any parameters passed through the route.
Redirect away from a component
Using the canLoad
lifecycle hook, we can redirect users. In the following example, we redirect a user to a /products
route. You would have this wrapped in a check to determine if the component loads or the user is redirected away.
Last updated