We're designing a new router for Angular 2.0. What capabilities should it have? Please share your thoughts and scenarios with us.
We're doing lots of design and prototyping work on Angular 2.0 now. I've had my hands in just about everything lately, including binding expressions, templating, the component model and routing. It's that last item, the router, that I'd love to hear from you about today.
I've implemented a router prototype, based on Durandal's router, but designed to work with Angular 2.0's templating and component model. It's very feature-rich and I'm quite happy with the design and capabilities. That said, I'd like to know what you want in a client-side router. If you are a Durandal user in particular, I'd like to know which features of Durandal's router you liked best. If you can share usage scenarios with me, that would really help. By doing this I'll have more concrete community usage information I can bring before the team and say "Here's why we really need this feature. Look at what people have already been doing."
Here's a few things you might mention:
- Child Routers
- Configuration and/or Conventions
I'd love for you to leave comments below describing your scenarios and features you like or would like in a router. Obviously, I can't make any promises about what we'll deliver. But we'll have a better chance of getting it right with your input.
P.S. If you really don't want to leave a comment, you can send me a personal email. You'll find my contact info here.
Rob is an internationally recognized UI development expert. He is the creator of the Caliburn.Micro and Durandal projects and an Angular 2.0 and Angular Material Design team member.