This repository was archived by the owner on Feb 26, 2024. It is now read-only.

Description
Subtitle: what about controllerAs?
Hi, thanks for closing #60. Got the plunk working now.
While working on it I managed to confuse myself tremendously, with a little assistance of ngFuturisticRouter.
I figured I would sum the sources of my confusion here, because I figure there is some additional documentation and/or possible changes needed to prevent others from mild headaches ;)
- the entire mapping from component name to files. (took me a while to find the documentations that pointed the seemingly fixed structure with the components folder)
- I followed the 'hello' example, in witch the router is in the AppController, and decided to create a route 'app' as in the getting-started.md That din't work out well ;)
- It took me also a while to figure out that the default bound controller for a 'route' is componentnameController, which is exposed to the template as componentname
- Still not (yet) clear, how to set a default route?
After I got around, and got the thing mostly working I had some observations.
Regarding to point 1, I suppose a lot of people would like to use the router in existing systems, this might be a giant PITA. While it's a great default for new builds, an easy override would be very helpful. (oh, it's also not very plunk friendly..)
regarding to point 3, what about controllerAs. I have already build a lot of stuff following the controller as vm convention. I do like that convention. But point 3 makes that a bit challenging.