These are chat archives for angular/angular.js

26th
Apr 2015
Josh Kurz
@joshkurz
Apr 26 2015 05:35
Angular 3 is the latest, Angular 2 is old school.
yibuyisheng
@yibuyisheng
Apr 26 2015 07:04
Angular 3?
What is Angular 3?
Kapil Dutta
@duttakapil
Apr 26 2015 07:23
asaik, most of the people haven't moved to even Angular 2 yet right? And now there is Angular 3?
Pascal Precht
@PascalPrecht
Apr 26 2015 08:06
@joshkurz I don't think your comment was very helpful.
There is no Angular 3.
Angular 2 is the new version the team is working on, but still in alpha and not ready to be used in production.
Angular 1 is the best Angular yet.
Kapil Dutta
@duttakapil
Apr 26 2015 11:14
Thanks @PascalPrecht
Quinntyne Brown
@QuinntyneBrown
Apr 26 2015 11:51
@PascalPrecht @jvandemo Does the new router and 1.4 support an app router on the Application controller and routers inside child components?
Quinntyne Brown
@QuinntyneBrown
Apr 26 2015 12:32
@PascalPrecht @jvandemo I created this plunker to help communicate the issue I see with 1.4 and the new router. http://plnkr.co/edit/rBvdtbI7Bn5C1VV0JV6E?p=info
Josh Kurz
@joshkurz
Apr 26 2015 14:28
@duttakapil my b, just messen with you. @PascalPrecht is 100% correct.
Quinntyne Brown
@QuinntyneBrown
Apr 26 2015 19:13
@PascalPrecht @jvandemo So it turns out child routers have not been implemented in the new router for Angular 1.4.
Gaute Løken
@gautelo
Apr 26 2015 20:20
@QuinntyneBrown I don't think that's the case. I believe the problem with your plunk is that you attempt to describe both of your routing configurations in one component. That's not how it's intended afaik. To get what you want, try making your app having two routes: welcome and list, both populating default outlet. Then, list is your sub-application and you place two outlets in its template; master and detail and configure the router for that subapplication.
Quinntyne Brown
@QuinntyneBrown
Apr 26 2015 21:05
@gautelo You are asking me to use the router again as a child router in the DetailController. That doesn't work. The router doesn't work in any controller other than the AppController. Child router is not implemented yet. Feel free to update the plnker. It came from a pretty credible source that child router is not implemented for Angular 1.4. If you believe you have the solution you can pull the router code and add your implementation as an example. (hint: There are no examples of using a child router)
Gaute Løken
@gautelo
Apr 26 2015 21:12
@QuinntyneBrown I'm not saying it'll work. I'm just saying that I'm not surprised that plnkr didn't. Also, no, I didn't mean you should use a child router in detail, that wouldn't make any sense. I meant you should have an abstraction on top of your two sibling routes; master and detail or list and detail, whichever you prefer. Anyway, I was just trying to be helpful and provide a different point of view as I didn't see a structure I thought would work in that plunk.
If you have a source claiming straight out that it's not implemented, please show it so I don't waste my time trying to get something working. I find it a bit incredible that it's not in at this point in time, if that's indeed the case...
Ghost
@ghost~5505633115522ed4b3dd48a6
Apr 26 2015 23:31
http://i.imgur.com/t5Dmqxg.png , guys, any idea?
Gaute Løken
@gautelo
Apr 26 2015 23:50
This message was deleted