> What kind of feedback are you looking for? This method seems to do what you suggest - puts two very common operations together.

Are the method & parameter names following the iOS/Objective-C naming convention?

Is the method name revealing its intent? In other words, if you see the following code in your app, will it be clear to you that it's performing login and passing the current user to the success callback?

```
[userRepository userByLoginWithEmail:email password:password success:^(LBUser *user) {
  // do something with user
  } failure:someErrorHandler];
```

> If my experience has anything to say about it, every app ever will use this in lieu of the individual calls.

Could you elaborate more on his? What would the app use the user object for?

The reason why I am asking: sending two request per login action seems quite expensive to me. A better solution is to include enough data in the login response so that the second request is not necessary.

Perhaps we should change the login response to include the full user object (instead of `userId` only)? I remember @seanbrookes needed similar functionality, where he wanted to run `Model.find` and include objects referenced via hasMany relationship in the response.

/cc @ritch @raymondfeng