Naming of user object field name is not consistent across API

[tomquirk]

I've noticed that the naming of the name field in user objects is inconsistent across the API. It is also somewhat ambiguous as to what name refers to.

Example:

• api.getFriendsList
  uses fullName to describe a user's full name 👍
• api.getUserInfo
  uses name to describe a user's full name 👎

There are possibly other places where this is also the case. This clearly hinders development.

I propose that, in any case where a user object includes a full name (e.g. Tom Quirk), that field is named fullName. This would improve clarity and consistency across the API and eliminate ambiguity between name and firstName. I would be happy to submit a PR for this given a consensus 😄

[Schmavery]

Sounds fine to me.

[bsansouci]

@tomquirk Let's do it! More consistency is better.