From 3bac29bf78abea2cd7ace1ac59771ef607f465ac Mon Sep 17 00:00:00 2001 From: Leo Horie Date: Sun, 8 Jan 2017 11:34:56 -0500 Subject: [PATCH] Clarify distinctions between RouteResolvers and components --- docs/route.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/route.md b/docs/route.md index 35549125..dde6b993 100644 --- a/docs/route.md +++ b/docs/route.md @@ -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}`