add "currentUri" to application controller

[ilovett]

Would be fantastic if you could some how build a url based on the currentPath... from within that function... Does a reverse look up of the model for controller and fills in the dynamic url pieces

Ember.Router.map(function() {
    this.route('index', { 'path' : '/' });
    this.resource('translation', { 'path' : '/t' }, function() {
        this.route('index', { 'path' : '/:translation_hash' });
    });
});

Ember.Router.reopen({
    'location' : (GLOBALS.location) ? GLOBALS.location : 'history',
    'onTransition' : function() {
        console.log(this.get('router.reverseUrl'));
        // "/t/cXwsd5"
    }.on('didTransition')
});

Why? Running apps on Phonegap / Cordova you will quickly find that "window.location" don't work so well... nah mean?

[ilovett]

Looking further into on('didTransition') I see that I can actually access the current url, even if the router location is set to none...

    'onTransition' : function() {
        App.LOG.info('router.js didTransition: '+this.get('url'));
        // "/t/cWsd5"
    }.on('didTransition')

What would be nice is if I could access "controllerFor" from here...

this.controllerFor('application').set('currentUri', this.get('url'));

OR better yet if Ember just decided to throw currentUri on the application controller, as a sibling next to currentPath

As an example of why this is useful, say you want to share a link, but you are running within a Phonegap/Cordova wrapper... it would be as easy as

shareUrl = 'http://example.com' + this.get('controllers.application.currentUri');

[rwjblue]

@machty - Thoughts on this one? Seems like a straightforward change, but at this point with three props being set maybe we are missing a higher abstract piece...

[ilovett]

I can understand not wanting to give access to the entire router from controllers, but there are some things in the router controllers may need to access

[wagenet]

@machty never got your input here.

[sandstrom]

I think it's safe to close this issue in favour of the RFC on a routing service: emberjs/rfcs#38

@ilovett Feel free to close this issue.

It isn't solved, but the RFC would be the right place to continue the discussion.