How do I add Public-Extension extensions to my iOS app?

You need to open the Swift Playground file in Xcode, copy the desired extensions, and paste them into your project's source files. There's no package manager support, so manual integration is required, which can be tedious for large projects.

Is Public-Extension better than writing my own Swift extensions?

Public-Extension offers community-vetted code that can save time and introduce best practices for common tasks. However, for project-specific needs, custom extensions might be more appropriate, so it's best used as a learning tool or for boilerplate reduction.

How often is Public-Extension updated?

New extensions are shared weekly via Twitter from @PublicExtension, with each tweet including sample usages and a link to the code in the repository, ensuring regular but informal updates.

Can I suggest an extension to Public-Extension?

Yes, you can DM suggested extensions on Twitter with a GitHub gist, as mentioned in the README. This community-driven approach allows for contributions but depends on Twitter engagement.

Public-Extension vs Swift Package Manager libraries for extensions

Public-Extension is great for discovery and experimentation in a playground, but SPM libraries offer better dependency management, versioning, and integration for production use. Choose based on whether you need informal learning or formal dependencies.

Does Public-Extension work with SwiftUI?

The extensions cover Swift language features and common types, so they can be used with SwiftUI projects, but they are not specifically tailored for SwiftUI, focusing more on general Swift enhancements.

Open-Awesome

Public Extensions

Swift

A weekly log of handy Swift extensions curated from the community.

GitHub

298 stars17 forks0 contributors

What is Public Extensions?

Public-Extension is a curated log of handy Swift extensions, updated weekly and shared via Twitter. It provides practical code snippets that extend Swift's standard library or common types, helping developers write more efficient and expressive Swift code. The project focuses on real-world usability with examples and documentation.

Target Audience

Swift developers, particularly those working on iOS, macOS, or other Apple platform projects, who want to discover and use community-vetted extensions to enhance their codebase.

Value Proposition

Developers choose Public-Extension for its regularly updated, practical extensions that are easy to integrate and experiment with via a Swift Playground. It offers a curated, community-driven approach to sharing Swift knowledge without the overhead of a full library or framework.

Overview

:wrench: A weekly log of handy Swift extensions

Use Cases

Best For

Finding ready-to-use Swift extensions for common tasks
Learning Swift language features through practical examples
Enhancing iOS or macOS projects with community-vetted code snippets
Experimenting with Swift extensions in an Xcode Playground
Staying updated on useful Swift patterns via weekly Twitter updates
Contributing Swift extension ideas to a community-driven project

Not Ideal For

Projects requiring stable, versioned dependencies integrated via package managers like Swift Package Manager
Teams needing comprehensive API documentation and formal support channels beyond playground examples
Developers working in environments without Xcode or access to Twitter for updates

Pros & Cons

Pros

Weekly Community Updates

New extensions are tweeted regularly from @PublicExtension with usage examples, ensuring a steady stream of fresh, practical content as stated in the README.

Interactive Learning Format

Extensions are provided in a Swift Playground file, allowing direct experimentation in Xcode with rendered documentation when enabled in the Utilities pane, per the README instructions.

Community-Driven Curation

Extensions are suggested by the Swift community via Twitter and GitHub gists, making it a collaborative resource that leverages collective knowledge.

Practical Code Snippets

Focuses on real-world usability with sample usages shared in tweets, helping developers quickly enhance their code with vetted extensions.

Cons

No Formal Packaging

Since it's distributed as a playground file, there's no easy dependency integration; users must manually copy and paste code into their projects, which can be error-prone.

Reliance on Social Media

Updates and suggestions are tied to Twitter, creating a barrier for developers not active on the platform or in regions with restricted access.

Lack of Version Control

The playground is updated weekly without versioning or a changelog, making it difficult to track changes, ensure compatibility, or revert to previous states.

Frequently Asked Questions

Related Projects

Parks And Recreation

Various Swift playgrounds, for fun and for profit.

Stars178

Forks11

Last commit1 year ago

URaimo's Playgrounds

Collection of Swift playgrounds used in my posts: From functional aspects of Swift to C interoperability.

Stars138

Forks13

Last commit7 years ago

Cocoa With Love Playgrounds

Swift Playground versions of select articles from Cocoa with Love.

Stars88

Forks3