reverse routes

[caullla]

Hi,
It would be very nice if you add some reverse functions.
I created something similar in my last project. And it looks like this one.

1. resolve - service, which have 2 methods. href and hash.

   > resolve.href( "route.name", [arg1, arg2] ) 
   /route/name/arg1/arg2/
   > resolve.hash( "route.name", [arg1, arg2] ) 
   #!/route/name/arg1/arg2/
   

2. url - filter.

   {{ "route.name" | ulr: [arg1, arg2] }}
   returns resolve.hash( "route.name", [arg1, arg2] )
   

3. redirectTo service

   redirectTo( "route.name", [arg1, arg2] )
   returns $location.path(resolve.href( "route.name", [arg1, arg2] ))
   

make sense?

[artch]

You created thins using route-segment or on your own?

There are some questions regarding such reverse mechanics. For example, what if multiple routes resolve to the same segment, which route should be resolved from this segment?

[caullla]

I see what you mean, but I didn't had this problem yet.
I'm new to angularjs, so I'm pretty sure that my solution isn't best.
I just use your rout-names.
http://pastebin.com/8twtTDU9

For now I have one problem, I can't determine hashPrefix, "#" or "#!". I checked source code, and it is not possible to get hasPrefix variable from outside.

[artch]

This proposal implemented in 1.3.0. Thanks!