Clarify distinctions between RouteResolvers and components
This commit is contained in:
parent
7c00aad19c
commit
3bac29bf78
1 changed files with 1 additions and 1 deletions
|
|
@ -109,7 +109,7 @@ Argument | Type | Required | Description
|
|||
|
||||
#### RouteResolver
|
||||
|
||||
A RouterResolver is an object that contains an `onmatch` method and/or a `render` method. Both methods are optional, but at least one must be present.
|
||||
A RouterResolver is an object that contains an `onmatch` method and/or a `render` method. Both methods are optional, but at least one must be present. A RouteResolver is not a component, and therefore it does NOT have lifecycle methods. As a rule of thumb, RouteResolvers should be in the same file as the `m.route` call, whereas component definitions should be in their own modules.
|
||||
|
||||
`routeResolver = {onmatch, render}`
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue