Greetings I want to clarify this question. For convenient routing in AngularJs (first version), we have a ui-router, a very convenient version of state-based routing. Studying Angular2, I expected there to see something similar out of the box, but alas ... I would like to ask a question, it was deliberately done and there are already some mechanisms that are better or just decided to do everything as in the first and then wait again for someone to make a ray what to eat If you need to use routing out of the box, then explain what is the difference between them and the advantage compared to ui-router pliz! A month ago, I started writing a great application on Angular1, simultaneously reading about the second one, and now I also wonder if I should continue to write on the first one, or better start writing on the second one, by the time I'm ready, I hope Angular2 will be released and will be full of lotions. What do you advise?
|
1 answer
It seems to me that now we are talking about navigating through states and navigating through components, including the possibility of making multi-level structures.
For migration, see: http://slides.com/christhielen/ui-router-ng1-to-ng2#/
Serge Markov Serge Markov
2,093 four eight
- As if yes, but the modules were added to rc5 again, now ui-router-ng2 has to be redone again. issue And anyway, depending on the state, we should manage the components ... - mistbow
|