DataModel.setScope behavior about angular-sailsjs-boilerplate-frontend HOT 5 CLOSED

The afterward result example would be helpfull.

from angular-sailsjs-boilerplate-frontend.

The result of the newValue of $scope.votesSurvey contains only register of VoteModel:

0:Object
  createdAt:"2016-08-21T08:18:47.000Z"
  createdUser:4
  id:26
  respuesta:19
  updatedAt:"2016-08-21T08:18:47.000Z"
  updatedUser:4
  userId: 4
  __proto__:Object
1:Object
  createdAt:"2016-08-21T08:19:09.000Z"
  createdUser:3
  id:27
  respuesta:19
  updatedAt:"2016-08-21T08:19:09.000Z"
  updatedUser:3
  userId: 3
...

from angular-sailsjs-boilerplate-frontend.

So is VotoModel for votesSurvey or just for votes?

from angular-sailsjs-boilerplate-frontend.

Actually...

In your resolve part you use AnswerModel and then in controller you assign that resolve object to $scope.votesSurvey = _votesSurvey; and then you set VotoModel.setScope($scope, false, 'votesSurvey');...

So there is the reason. First in your resolve part you use model A and then in controller you set model B to be the same, so just a logic problem on your end - and not actual issue about this project.

from angular-sailsjs-boilerplate-frontend.

Well. votesSurvey is a join between AnswersModel and VoteModel.
Meanwhile, a solved this with injected _votes -> return VoteModel.load(), after that I setScope to votes (that contain all votes for all surveys) and inside the controller make the filter.
But, for curiosity, is there a way to injected a join tables and make this join tables visible to the scope/socket events? Thanks

from angular-sailsjs-boilerplate-frontend.