Angular 2 Survey Results

Post by christhielen » Sat, Sep 05, 2015, 2:37 AM UTC

mdngtcdr wrote: post #76

nateabele wrote: post #22

Hey, UI Router lead dev here. I'm interested in any & all feedback people have regarding Component Router vs. UI Router, what they like/don't like, and whether or how much they'd like to see UI Router support for Angular 2.

Hi, I've been using AngylarJS & UI-Router for about 2 months. It's great. Some of the shortcomings that struck me were- Lack of "routing state" - integration with the history API or means to go to "previous" state etc. No clarity in handling errors from "resolve" - Since there is no controller any failed AJAX request fails silently. Ability to pass data (not params, more like a model) between states. This I think spa…

Hi, ui-router dev here. 1.0 is adding a global transition error handler which you can customize. The handler will be noisy by default (log to the console).

To send data in a transition, add a non-url param to the target state. We added objects-as-params (url based or not) in I think 0.2.12

Post by christhielen » Sat, Sep 05, 2015, 2:59 AM UTC

bubersson wrote: post #70

nateabele wrote: post #22

Hey, UI Router lead dev here. I'm interested in any & all feedback people have regarding Component Router vs. UI Router, what they like/don't like, and whether or how much they'd like to see UI Router support for Angular 2.

We started using ui-router recently and from quick profiling of rendering it looks like a lot of time is spent in ui-router transitions (chained promises) and in generating/validating ui-sref links. I don't know if this will get linearly worse with increasing size of application, but anyway this is why I'm interested in checking out Component Router. Do you have any pointers to differences between Component Router an…

Another ui-router dev here. I've also never profiled transitions for performance (frankly, I don't think I've seen it mentioned before). I'd love to hear anything else you recall about your findings.

As for the ui-sref, there should be only one watcher per, and should only really impact perf if the target params change. Does that align with what you remember seeing?

Re: Angular 2 Survey Results

Re: Angular 2 Survey Results