$ show ochococo/OOD-Principles-In-Swift
OOD-Principles-In-Swift is an educational repository that teaches Robert C. Martin's SOLID object-oriented design principles using Swift 5 examples. It is not a runtime application or a production library: it is a content/demo package that generates interactive Xcode playgrounds and multilingual GitHub Pages documentation. The canonical code lives in source/SOLID/*.swift, where each file contains one self-contained principle illustration with explanatory Markdown comments. Bash scripts named generate-playground-*.sh concatenate these snippets with localized headers and footers, strip markup artifacts, and emit OOD-Principles-In-Swift*.playground/contents.swift plus README-*.md for a dozen languages. When consumed, the primary entry point is OOD-Principles-In-Swift.playground/contents.swift, which renders five SOLID sections in Xcode's playground UI. The repo also acts as a Jekyll site via _config.yml and _layouts/default.html, hosting the translated READMEs on GitHub Pages. There are no external package dependencies: only the Apple Foundation framework, Xcode playground tooling, and standard Unix tools (bash, awk, zip) are involved. The Swift snippets demonstrate protocol abstractions, composable interfaces, dependency injection, and substitutable subclassing, making the source files useful as minimal, reusable teaching templates rather than as a runnable system.
The LLM identified 5 files worth highlighting for reuse:
Minimal SRP demonstration: PodBayDoor encapsulates state behind Openable and Closeable protocols, while DoorOpener and DoorCloser each depend only on the narrow protocol they need. Reusable as a clean template for role-segregated Swift types.
Shows OCP with a Shooting protocol, LaserBeam and RocketLauncher implementations, and WeaponsComposite consuming [Shooting]. The composite can be extended with new weapon types without modifying existing classes, making it a compact strategy/composite style example in Swift.
Uses a RequestError subclass of NSError to show that a caller returning NSError can still be substituted by the subclass, and the richer type can be recovered by downcasting. A compact lesson in behavioral substitutability, though written against legacy Foundation types.
Splits capabilities into LandingSiteHaving, Landing, PayloadHaving, and PayloadFetching so clients like InternationalSpaceStation and SpaceXCRS8 depend only on the role protocols they actually use. Demonstrates Swift protocol composition as a way to keep interfaces fine-grained.
Illustrates DIP by injecting a TimeTraveling protocol into EmmettBrown instead of a concrete DeLorean class. This is a compact, dependency-injection-ready template for decoupling high-level policy from low-level implementation in Swift.