Hi,
In v0.8.3.23, Creator node appear once only but in 0.9.1.x Creator node appear twice, once as attribute at root level and once as a sub node of TweetDTO node.
I am not sure of what you mean. In 0.9.x.x, the tweets are composed of a logic class (ITweet) and a class that host the data (ITweetDTO). The ITweet is the class the developers should be using but they can use the ITweetDTO in order to pass it through a service layer if needed.
In a few words, just use the ITweet and never access the ITweetDTO, you don't need to.
In v0.8.3.23, Creator has followerids and friendsids populated as arrays of long numbers, but in v0.9.1.x, these two field are always set to NULL.
Well the issue with these properties is that they were differed properties. It means that when the user requested user.FriendIds, Tweetinvi was doing the query for them without the developer knowing about it. It meant that developers could see their rate-limit changed without them having a good knowledge of why it had decreased.
In 0.9.x.x they are just variable to store information so that you can do this:
Describing this I have just realized that these variable does not have a setter in the interface this will be added for 0.9.2.0 which is coming in few days.
I was thinking of renaming these variables user.FriendsStore or user.PlaceHolder but I cannot find a name that I am happy with.
Please feel free to make any suggestion.
Regards,
Linvi
In v0.8.3.23, Creator node appear once only but in 0.9.1.x Creator node appear twice, once as attribute at root level and once as a sub node of TweetDTO node.
I am not sure of what you mean. In 0.9.x.x, the tweets are composed of a logic class (ITweet) and a class that host the data (ITweetDTO). The ITweet is the class the developers should be using but they can use the ITweetDTO in order to pass it through a service layer if needed.
In a few words, just use the ITweet and never access the ITweetDTO, you don't need to.
In v0.8.3.23, Creator has followerids and friendsids populated as arrays of long numbers, but in v0.9.1.x, these two field are always set to NULL.
Well the issue with these properties is that they were differed properties. It means that when the user requested user.FriendIds, Tweetinvi was doing the query for them without the developer knowing about it. It meant that developers could see their rate-limit changed without them having a good knowledge of why it had decreased.
In 0.9.x.x they are just variable to store information so that you can do this:
var user = User.GetLoggedUser();
user.Friends = user.GetFriendIds().ToList();I was thinking of renaming these variables user.FriendsStore or user.PlaceHolder but I cannot find a name that I am happy with.
Please feel free to make any suggestion.
Regards,
Linvi