Technical Test

This application consists in two UIViewController. The first one has an
UITableViewController linked to CoreData. This table shows what is
stored order by rating. Each cell displays one picture, name and rating.
The second view is a detail visualization of each picture. It shows
name of the photo, description (maximum 3 lines), user avatar and user
name, name of the camera, aperture, lens, focus, iso and location. This
view only shows the available info.

Whenever the application is launched, it shows data that is currently
stored in the local SQLite and checks for an update automatically. If
there are a response, the application erases all content and stores the
new one. If the user scrolls at the bottom the the table it will ask
for more pictures.
It is a bad practice for my side. My last boss did not like camel cases in
coredata objects.

2014-11-03 14:56 GMT+01:00 Rubén Méndez <notifications@github.com>:

> In agpaton_PopularPhotos/Services.m:
>
> > +
> > ++ (void) UpdateCoreDataCacheWithJSON:(NSArray*)photoList andManagedObjectContext:(NSManagedObjectContext *)childMOC;
> > +{
> > +    NSError *error;
> > +
> > +    for (NSDictionary *photo in photoList) {
> > +
> > +        NSNumber *ID = [photo objectForKey:@"id"];
> > +
> > +        Photo *p = [self GetPhotoWithID:ID andManagedObjectContext:childMOC];
> > +
> > +        if (!p) {
> > +            p = [NSEntityDescription insertNewObjectForEntityForName:@"Photo" inManagedObjectContext: childMOC];
> > +        }
> > +
> > +        p.photo_id = ID;
>
> Why don't you use camelCase?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/TheRanking/theranking-ios-candidates/pull/4/files#r19733364>
> .
>