{"action":"opened","issue":{"url":"https://api.github.com/repos/katesi/rottenTomatoes-2/issues/1","labels_url":"https://api.github.com/repos/katesi/rottenTomatoes-2/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/katesi/rottenTomatoes-2/issues/1/comments","events_url":"https://api.github.com/repos/katesi/rottenTomatoes-2/issues/1/events","html_url":"https://github.com/katesi/rottenTomatoes-2/issues/1","id":57709573,"number":1,"title":"Review notes","user":{"login":"codepathreview","id":7917093,"avatar_url":"https://avatars.githubusercontent.com/u/7917093?v=3","gravatar_id":"","url":"https://api.github.com/users/codepathreview","html_url":"https://github.com/codepathreview","followers_url":"https://api.github.com/users/codepathreview/followers","following_url":"https://api.github.com/users/codepathreview/following{/other_user}","gists_url":"https://api.github.com/users/codepathreview/gists{/gist_id}","starred_url":"https://api.github.com/users/codepathreview/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/codepathreview/subscriptions","organizations_url":"https://api.github.com/users/codepathreview/orgs","repos_url":"https://api.github.com/users/codepathreview/repos","events_url":"https://api.github.com/users/codepathreview/events{/privacy}","received_events_url":"https://api.github.com/users/codepathreview/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-14T22:48:32Z","updated_at":"2015-02-14T22:48:32Z","closed_at":null,"body":"Hi @katesi  created  my own issue to comment on your new repo\r\n\r\n* repo looks fine, just add a .gitignore. What I always do is first create the repo on Github, clone it and then copy project files to the repo\r\n* Nice code styling. The New York Times has a good summary of appropriate Objective-C coding conventions, you should take a quick look [here](https://github.com/NYTimes/objective-c-style-guide).\r\n* Nice work with the header files. You should always try to minimize the number of properties and methods in the header files and move all private properties and methods into the class extension (the @interface block in the .m file).\r\n* In future homework, we will cover how to implement models that can deserialize from an NSDictionary. It might be interesting to check out the Mantle project for a lightweight ORM.\r\n* Your custom Movie cell should have a property called `movie`. In the custom setter of `movie`, you should configure the various labels and images. This decouples your custom cells from the table view controllers.\r\n* Nice work loading the images asynchronously.\r\n* Nice work setting up the proper modes for the images so that they are not stretched.\r\n* Nice work implementing the error message on network failure.\r\n\r\nIn general, you should challenge yourself to create visually polished applications. That's where you'll find all the rough edges of the iOS framework and earn the next level of mastery.\r\n\r\n--dirk\r\n"}}