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 Simple iPhone App with Swift 2.0 Getting Started with iOS Development Swift Recap Part 1

Aaron Glaesemann
Aaron Glaesemann
11,303 Points

I can't get the Tag type to read correctly in my string assigned to postDescription.

I've tried initializing the Post struct with no different results. I'm not sure how I can get the sentence to read as "In Cold Blood by Capote. Filed under mystery" instead of "In Cold Blood by Capote. Filed under Tag(name: "mystery")". I don't know how to access the value for tag as a value type of Tag in my firstPost instance to properly use in my string.

1 Answer

Hi Aaron

Have a look at this solution to see if that makes sense to you:

struct Tag {
    let name: String
}

struct Post {
    let title: String
    let author: String
    let tag: Tag

    func description() -> String {
        return "\(title) by \(author). Filed under \(tag.name)"
    }
}

let firstPost = Post(title:"iOS Development", author:"Apple", tag: Tag(name: "swift"))
let postDescription = firstPost.description()

Accessing the name property of the tag instance is done with dot notation inside the string interpolation.

I hope that makes sense?

Steve.

Aaron Glaesemann
Aaron Glaesemann
11,303 Points

Oh man, that's it! I thought I tried that but I was actually trying to use the capitalized Tag from the original struct declaration.

Thank you for the clarification!!!

No problem - glad you got it fixed! :-)

Steve.