A handy collection of more than 500 native Swift extensions to boost your productivity.

I wanted to contribute, but I'm very inexperienced in contributing to open source projects. I'd appreciate it if you could tell me what's missing :)

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

[v] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

What did you do?

Set shadowOffset, shadowColor, shadowRadius inspectable value on UILabel.

What did you expect to happen?

UILabel with proper shadow

What happened instead?

shadowOffset is not applied, because UILabel has shadowOffset property. So shadow is always above text, because layer.shadowOffset default value is (0, -3) (Also UILabel has shadowColor property.)

SwifterSwift Environment

• SwifterSwift version: 4.6.0
• Xcode version: 10
• macOS version running Xcode: 10.14.2
• Swift version: 4.2
• Platform(s) running SwifterSwift: iOS

Demo Project

Please link to or upload a project we can download that reproduces the issue.

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

This extension allows to create an NSColor or UIColor with different colors for light mode and dark mode. I created separate NSColorExtensions.swift and UIColorExtensions.swift files, because NSColor and UIColor use different APIs for this problem and can't be unified.

I couldn't figure out how to create a test for macOS, because it uses NSAppearance instead of UITraitCollection. Any suggestions?

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

🚀 Fixed #653. Added withoutDuplicates(keyPath:) to Array.

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

Describe the bug The package will fail to build and install when used inside a project being compiled on Xcode 14 beta, with an ambiguous use of 'makeIterator()' error.

To Reproduce

1. Add SwifterSwift as a package inside an iOS project.
2. Open project in Xcode 14 beta.
3. Attempt to build app.

Expected behavior The SwifterSwift package will not fail to build when using Xcode 14 beta.

Additional context

Here's a screenshot of the error:

I'm about to open a PR which addresses this issue!

• [x] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

Sometimes I need the image to be on the right or below the text. So add imageRightText on UIButton

| type | imageAboveText: false | imageAboveText: true  | | --- | --- | --- | | imageRightText: false| Image/Text |

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

🚀

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

…o specify Swift version of pod target itself.

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [ ] New extensions are written in Swift 4.
• [ ] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
• [ ] I have added tests for new extensions, and they passed.
• [ ] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [ ] All extensions are declared as public.
• [ ] I have added a changelog entry describing my changes.

Adding the function to create a UIStackView from an Array of UIViews. Taking the defaults and parameter docs from Apples Defaults.

Solves #399

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 4.
• [x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

https://github.com/SwifterSwift/SwifterSwift/blob/master/LICENSE

MIT License
-- Copyright (c) 2015-2017 SwifterSwift (https://github.com/swifterswift)
++ Copyright (c) 2015-2018 SwifterSwift (https://github.com/swifterswift)

🚀

Hello. Thank you for SwifterSwift. Fix #1066.

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

🚀 Is your feature request related to a problem? Please describe. Hello. Thank you for SwifterSwift. Found out that you have s[safe: 10] and s[safe: 1..<10]. But what about s[safeFrom: 3] and s[safeTo: 10]?

Describe the solution you'd like Add subscript(safeFrom lowerBound: Int) -> String? and subscript(safeTo upperBound: Int) -> String? to StringExtensions.swift.

Describe alternatives you've considered Nothing.

Additional context Nothing.

• [x] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

🚀 fixes #1054

Checklist

• [x] I checked the Contributing Guidelines before creating this request.
• [x] New extensions are written in Swift 5.0.
• [x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
• [x] I have added tests for new extensions, and they passed.
• [x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
• [x] All extensions are declared as public.
• [x] I have added a changelog entry describing my changes.

Describe the bug SwifterSwift declares an extension to HealthKit that breaks compilation on macOS because Healthkit is only available on macOS from v13

To Reproduce Steps to reproduce the behavior:

1. Create a project on Xcode 14 on Ventura and try to include SwifterSwift with a target deployment < Ventura

Expected behavior Code should compile

Desktop (please complete the following information):

• OS: macOS 13
• Xcode Version : 14.1
• Project: deployment = BigSur and uses macOS13 SDK to compile

Additional context We created a fork and simply modified the @availability predicate in HKActivitySummaryExtensions

@available(watchOS 2.2, macOS 13.0, *)

• [X ] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

We have 2 basically the same functions for generating a random string which only differ in their signatures.

https://github.com/SwifterSwift/SwifterSwift/blob/04d474ade1aa7d8e6bde9a65d5f8d1a3595dc3a0/Sources/SwifterSwift/SwiftStdlib/StringExtensions.swift#L764-L778

and

https://github.com/SwifterSwift/SwifterSwift/blob/04d474ade1aa7d8e6bde9a65d5f8d1a3595dc3a0/Sources/SwifterSwift/SwiftStdlib/StringExtensions.swift#L1159-L1177

I suggest we only leave the static one, so it will be the same as Int.random(in:) in Foundation