Swiftpack.co -  theblixguy/Invalidating as Swift Package
Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
theblixguy/Invalidating
Backports the new @Invalidating property wrapper to older platforms
.package(url: "https://github.com/theblixguy/Invalidating.git", from: "0.1.0")

ViewInvalidating

A property wrapper that backports the new @Invalidating property wrapper to older versions of iOS/tvOS/macOS. For more information on this new property wrapper, see the WWDC 2021 talk "What's new in AppKit" for a brief introduction.

The syntax and types closely follows what Apple is doing, so when it's time to finally update your project's deployment target to iOS 15+/tvOS 15+/macOS 12+, you can easily migrate to using Apple's version by making very minimal changes. See the migration section for more info!

Usage

Annotate your Equatable properties with @ViewInvalidating and provide options that will be used to invalidate the view whenever the property's value changes:

final class MyView: UIView {
  // Calls setNeedsLayout()
  @ViewInvalidating(.layout) var cornerRadius: CGFloat = 12.0
  
  // Calls setNeedsLayout() then setNeedsUpdateConstraints()
  @ViewInvalidating(.layout, .constraints) var heightConstraintValue: CFloat = 200.0
  
  // Calls setNeedsLayout() then setNeedsUpdateConstraints() then invalidateIntrinsicContentSize()
  @ViewInvalidating(.layout, .constraints, .intrinsicContentSize) var magicProperty: CGFloat = 1234.0

You can initialize the property wrapper with up to 10 options. You can of course add extensions to support more options though, but realistically speaking you'll likely never have a need to pass more than a few of them!

By default, there is support for a total of 5 invalidation options per platform:

Common

  • Layout
  • Display
  • Constraints
  • Intrinsic Size

macOS only

  • Restorable State

iOS 14+ only

  • Configuration

Adding custom invalidators

You can add custom invalidators by creating a type that conforms to UIViewInvalidatingType or NSViewInvalidatingType protocol (depending on the target platform) and implementing the invalidate method requirement:

extension Invalidations {
  struct Focus: UIViewInvalidatingType {
    static let focus: Self = .init()

    func invalidate(view: UIView) {
      view.setNeedsFocusUpdate()
    }
  }
}

You can then expose it to the property wrapper by extending the InvalidatingStaticMember type:

extension InvalidatingStaticMember where Base: UIViewInvalidatingType {
  static var focus: InvalidatingStaticMember<Invalidations.Focus> { .init(.focus) }
}

Note:

If you're using Xcode 13, you should do this instead:

extension UIViewInvalidatingType where Self == Invalidations.Focus {
 static var focus: Self { .focus }
}

The InvalidatingStaticMember type only exists to workaround some language limitations which have been addressed in Swift 5.5, which ships with Xcode 13. So if you're on the latest Xcode, you do not need to use the workaround. The InvalidatingStaticMember will also be unavailable.

Then you can use your new invalidator on @ViewInvalidating:

final class MyView: UIView {

  // Calls setNeedsLayout() and Focus.invalidate(self)
  @ViewInvalidating(.layout, .focus) var customProperty: CGFloat = 1.0
}

Requirements

  • Deployment target of iOS 11+, tvOS 11+ or macOS 10.11+
  • Xcode 11 or above

Installation

Add the following to your project's Package.swift file:

.package(url: "https://github.com/theblixguy/Invalidating", from: "0.1.0")

or add this package via the Xcode UI by going to File > Swift Packages > Add Package Dependency.

Migration to iOS 15+/tvOS 15+/macOS 12+ deployment target

When it's time to update your project's deployment target to iOS 15+/tvOS 15+/macOS 12+, you will need to make some very minor changes to your code to make it compatible with Apple's @Invalidating and related types.

The types that ship with this package have been annotated with @available and contain the right mappings to Apple's types on its renamed argument to make it super easy for you to update your code. Once you have update the deployment target, you will see some errors:

Migration Fix-it Migration Fix-it

As you can see, they all offer a fix-it to automatically change the type names. With a click of a button, the errors disappears without you even having to manually rename them:

Migration Fix-it Migration Fix-it

License

MIT License

Copyright (c) 2021 Suyash Srijan

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

GitHub

link
Stars: 49
Last commit: 3 weeks ago

Ad: Job Offers

iOS Software Engineer @ Perry Street Software
Perry Street Software is Jack’d and SCRUFF. We are two of the world’s largest gay, bi, trans and queer social dating apps on iOS and Android. Our brands reach more than 20 million members worldwide so members can connect, meet and express themselves on a platform that prioritizes privacy and security. We invest heavily into SwiftUI and using Swift Packages to modularize the codebase.

Release Notes

Name migration
4 weeks ago

Unfortunately, the property wrapper needs to be renamed otherwise name lookup will treat a reference to Invalidating and other types as ambiguous in Xcode 13 due to conflicts with the same type name in UIKit/AppKit. I did not expect this behavior because I assumed the new types would be effectively unavailable on lower deployment targets and the compiler will allow me to shadow those types with mine, however that does not seem to be the case.

I have tried to isolate the changes to just the name of the property wrapper slightly (to ViewInvalidating), removing the Invalidations type from the UIView/NSView namespace and making it standalone and renaming UIViewInvalidating/NSViewInvalidating by adding a Type suffix to it.

These changes alone were enough to resolve the problems while still making it super easy to migrate to the new type names when the deployment target is changed to iOS 15+/tvOS 15+/macOS 12+. This is achieved by adding @available annotations and providing the new type names for the renamed argument. The renamed type name is then provided as a fix-it on the availability errors making it very easy for the user to migrate without manually needing to rename anything.

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API