Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

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

Qasa Lee
Qasa Lee
18,915 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,772 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,915 Points

That makes sense. Thanks!