Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

iOS Build a Restaurant Reviews App Simplifying Networking Code Displaying Restaurants Around Us

Qasa Lee
Qasa Lee
18,916 Points
Posted by Qasa Lee
Qasa Lee
18,916 Points

How about declaring "client" property (in YelpSearchController.swift) as "var" rather than "lazy var"?

// Why using "lazy"???
    lazy var client: YelpClient = {
        let yelpAccount = YelpAccount.loadFromKeychain()
        let oauthToken = yelpAccount!.accessToken // Bad Practice due to force unwrapping!

        return YelpClient(oauthToken: oauthToken)
    }()

inside this closure there ain't no property of YelpSearchController, why still "lazy"?

1 Answer

Nathan F.
Nathan F.
30,773 Points
Nathan F.
Nathan F.
30,773 Points

Since we're instantiating another class and loading from keychain--something that may require user authorization--use of a lazy property means that this work won't be done until we absolutely need it, such as in a function call that relies upon this property. At least that's how I understand why we're using a lazy property here.

Qasa Lee
Qasa Lee
18,916 Points
Qasa Lee
Qasa Lee
18,916 Points

That makes sense. Thanks!