Reply Status Update

[pamo]

@timothy1ee I pushed my latest changes. Apart from some auto-layout issues I'm having in the tweet view controller, I'm stuck on forming the reply payload. I know the username of the recipient has to be in the tweet text and their tweet id has to be passed as a parameter, but I can't figure out why those values aren't being picked up when I move from one controller to the next. Could you take a look?

https://github.com/pamo/Tweety/commit/45e4abe984515babd7c113a27f241e3fb3bdf816

[pamo]

Issue was passing the username value to the ComposeViewController from TweetViewController as a NSString property. Couldn't figure out how to pass it so I passed it as a UILabel instead. Seems to be working now.

[timothy1ee]

Pam, I'm glad you were able to get things generally working. You've successfully augmented the networking and model layers. You've also played around with basic navigation.

• Be sure to try making the rows dynamic in height. It's a common requirement in iOS, so good to practice. If you try it, you'll find that your Auto Layout constraints for the image view are not correct.
• After I compose a Tweet, I would expect to see the newly created Tweet in the feed.
• There's no way to delete a retweet or favorite.
• You should implement pull to refresh and infinite scrolling.

The main takeaways for this homework were:

• How to handle dynamically sized rows in table views.
• How to implement and debug Auto Layout in the Tweet Cell, Compose view, and Tweet view.
• How to implement nav stack and modal navigation.
• How to augment a networking client.
• How to augment a model, adding serialization/deserialization code, and formatting code.

Here's my checklist of things I'm looking at when I'm reviewing this project.

• Is the Objective-C code styling consistent with standards?
• Did you augment the API client with the methods for updating status, reply, retweet, favorite? Note that there is a separate endpoint for removing a retweet or favorite.
• Did you augment the Tweet model? Note that for the embedded user, you should instantiate a User object and have the User class do the deserialization, instead of navigating to user.screen_name in the Tweet model.
• Were the Auto Layout constraints correct for all the views?
• Was the navigation implemented correctly either manually or via segues?
• Was pull to refresh implemented?
• Was infinite scrolling implemented?