$sails.get not called when returned as resolve for anguilar-ui-router

[Deleted user]

If I try to use $sails in a resolve like $http is used in the ui-router docs:

.state('base.main.register', {
    url: '/register',
    templateUrl: 'modules/site/register.html',
    resolve: {
        campuses: function($sails) {
            return $sails.get('/resource').
                then(function (res) {
                    console.log(res);
                });
        }
    }
}

1)It never gets called and 2) the page never finishes loading. If I, however, simply move the code out of the resolve and into a controller, it works great.

.state('base.main.register', {
    url: '/register',
    templateUrl: 'modules/site/register.html',
    controller: function ($sails) {
         $sails.get('/resource').
              then(function (res) {
                  console.log(res);
              });
    }
}

[janpantel]

Please remove the then console.log from your resolve and report :)

[Deleted user]

Your smile got me excited! Same behaviour though... :(

[janpantel]

Have you tried to asign an error handler to the promise and checked if there is a request hitting the backend?

[TheSharpieOne]

If you have a fiddle or some live example, it would be very helpful.
Are any errors being thrown to console? Can you check your network tab to see if the socket connection is being made and if the socket frames show any communication?

[Deleted user]

I don't know how I would setup a fiddle or plunker without hosting the sails backed somewhere...

What tools would be good to look at the socket connection information?

[janpantel]

Just add a console.log to your backend controller to check if you request hits the server :)

[tsterker]

@circuitlego This might be related to #21, where the $sails socket is not yet connected.
Maybe you could try console.log($sails.socket.connected) in your resolve function
and if it returns false, then you could use this snippet as a (crude) workaround:
#21 (comment)

If you include this wrapper factory, the only change you would need in your code is to replace all $sails occurrences with $sailsPromised.

[TheSharpieOne]

@circuitlego If you use Google Chrome you can view socket information in the DevTools under the Network tab. Here is an older post explaining how: http://stackoverflow.com/questions/8952773/chrome-web-inspector-web-socket-debugging

[TheSharpieOne]

Just looking at this again with fresh eyes... you need to return something in your .then(function(){...}) so it can be passed to the next step/'link' in the chain. With what you have, resolve will be getting undefined.

Here is a stupid quick example of this chaining http://jsfiddle.net/TheSharpieOne/8rmuqj8q/
In the console your can see what value gets passed to each of the .then()s The first one gets the value that was passed, but because it doesn't return it (return val), the next function gets undefined/nothing.

In your example, return res at the end of the function or just get rid of the .then().

[TheSharpieOne]

Closing this issue as it is not active. Try the latest release and if you are still experiencing this issue, please re-open it.