How does the app know a component is a page

Question

Now that the @Page decorator had been deprecated, how does the app differentiate between a component that should be used as part of a page and a component that represents a page you can navigate to?

The only difference I see that page components have no selector property defined in the @Component decorator.

score 5 · Accepted Answer · answered Jun 14 '16 at 14:34

5

A component is considered to be a page if it's pushed to the navigation controller's stack.

A selector property is optional in an Angular2 component. You only need it when you want to use the component as an HTML element in the template of another component.

I think the reason @Page was deprecated, is that there wasn't so much difference between the two in the first place.

answered Jun 14 '16 at 14:34

Yaron Schwimmer

5,327
5
36
59

So there is nothing stopping you adding a component with a `selector` to the navigation stack? no errors? – user1275105 Jun 14 '16 at 16:52
I haven't tried that, but I would guess that it won't be a problem. – Yaron Schwimmer Jun 14 '16 at 18:47

How does the app know a component is a page

1 Answers1

Linked