Book Image

Hands-On Design Patterns with Swift

By : Florent Vilmart, Giordano Scalzo, Sergio De Simone
Book Image

Hands-On Design Patterns with Swift

By: Florent Vilmart, Giordano Scalzo, Sergio De Simone

Overview of this book

Swift keeps gaining traction not only amongst Apple developers but also as a server-side language. This book demonstrates how to apply design patterns and best practices in real-life situations, whether that's for new or already existing projects. You’ll begin with a quick refresher on Swift, the compiler, the standard library, and the foundation, followed by the Cocoa design patterns – the ones at the core of many cocoa libraries – to follow up with the creational, structural, and behavioral patterns as defined by the GoF. You'll get acquainted with application architecture, as well as the most popular architectural design patterns, such as MVC and MVVM, and learn to use them in the context of Swift. In addition, you’ll walk through dependency injection and functional reactive programming. Special emphasis will be given to techniques to handle concurrency, including callbacks, futures and promises, and reactive programming. These techniques will help you adopt a test-driven approach to your workflow in order to use Swift Package Manager and integrate the framework into the original code base, along with Unit and UI testing. By the end of the book, you'll be able to build applications that are scalable, faster, and easier to maintain.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Becoming a maintainer, tips and tricks


Maintaining an open source project is fun, full of surprises, and sometimes hard. The following tips have been gathered from experience and discussions with other maintainers.

The README.md file

The README.md file is perhaps the most important file in your project. It describes what your project does.

It has an .md extension, so it’s written in Markdown, the same language as your Swift documentation, so if you were not previously familiar with it, you should be by now.

Ideally, it should contain multiple sections:

  • A title that should match the repository, folder, and package-manager names
  • A short description, which is the hook, indicating what your project does, in a nutshell
  • A table of contents, if your readme is very long
  • Instructions for installation
  • Instructions on how to use your project
  • Instructions on how to contribute to the project
  • The license for the code you are open sourcing

I didn’t invent those on my own, but a standard readme specification is actively...