$sailsSocket.on() function is 'undefined'

[key10]

I'm in the process of switching our code from using angular-sails to using your angularSails, however, it seems that there are some issues.

1. in your repo, you have an examples folder with both a www and an assets folder. These two seem to be using different approaches to including the angularSails (www seems to be using something completely different). So it is not clear which is the advised way.
2. [the main issue I am writing for] when adding the 'sails.io' dependency into my module declaration, and injecting '$sailsSocket' into my controller, it is saying that 'on' ($sailsSocket.on()) is undefined. Looking at the dist/ngsails.io.js file, line 587 has 'createShortMethods' for 'get','delete','head' and then line 634 has the 'createShortMethodsWithData' function for 'post','put'. The comment block starting on line 617 mentions the on method, but it doesn't seem to be included in either of these two function calls.
3. a detailed example on the JSDocs would be great for the preferred implementation of this.

Any help that you guys can provide would be a great help!!

[key10]

So I just tried using the $sailsSocket.subscribe() function in place of where we were using $sails.on (from angular-sails), and it seems to have the same effect of listening for an event from the server and calling a given function.

So my next question is: What is the difference between the .on() and the .subscribe() on your API documentation site?

Thanks

[nbiton]

After encountering the same issue, I dug into the code and noticed that the "subscribe" method is directly mapped to io.socket.on(), so there shouldn't be any difference.

[key10]

@nbiton : thanks for your response. I ended up getting ahold of Rob (the main contrib to this project) via email, and he said that for all intents and purposes the 'subscribe' method should accomplish what I want. He was hoping to get a new build pushed soon with the updated use of the 'on' method.