Project structure and Swift Package Manager basics - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of the Swift Package Manager (SPM)?

Swift Package Manager helps you manage and share Swift code by handling dependencies, building, and distributing packages easily.

beginner

Name the default file that defines a Swift package's configuration.

The file is called Package.swift. It describes the package's name, products, dependencies, and targets.

intermediate

What are 'targets' in a Swift package?

Targets are the basic building blocks of a package. Each target can be a module or a test suite, containing source files to compile.

beginner

Where should source files be placed in a Swift package project structure?

Source files go inside the Sources/ directory, organized by target name. Test files go inside Tests/ similarly.

intermediate

How do you add an external dependency to a Swift package?

You add the dependency URL and version in the dependencies array inside Package.swift. Then you specify which targets use it.

Which directory contains the main source code in a Swift package?

A Sources/

B Tests/

C Build/

D Docs/

The Sources/ directory holds the main source code files for the package.

What file do you edit to define your Swift package's dependencies?

A README.md

B Info.plist

C main.swift

D Package.swift

Package.swift is the configuration file where dependencies are declared.

In Swift Package Manager, what is a 'target'?

A A test report

B A folder for documentation

C A group of source files compiled together

D A build configuration

A target is a set of source files compiled into a module or test suite.

Where do you put test files in a Swift package?

A Docs/

B Tests/

C Build/

D Sources/

Test files go inside the Tests/ directory, organized by target.

Which command initializes a new Swift package?

A swift package init

B swift build

C swift run

D swift test

The command 'swift package init' creates a new Swift package with the default structure.

Explain the basic folder structure of a Swift package project and the role of each folder.

Think about where your code and tests live and how the package knows about them.

Describe how you add and use an external dependency in a Swift package.

Focus on editing Package.swift and how targets relate to dependencies.