Question 1

How do I store a Swift enum in NSUserDefaults with TypedDefaults?

Accepted Answer

Define your enum to conform to DefaultsConvertible by implementing serialize() to return a raw value (e.g., Int) and init?(_ object:) to initialize from that raw value, as demonstrated in the CameraConfig example with the Size enum.

Question 2

TypedDefaults vs Codable for UserDefaults in Swift – which is better?

Accepted Answer

TypedDefaults offers compile-time type safety and dependency injection for testability, but Codable provides automatic serialization with less code for many types. Choose based on whether you prioritize testing flexibility or reduced boilerplate.

Question 3

Can I use TypedDefaults with SwiftUI?

Accepted Answer

Yes, TypedDefaults can be integrated into SwiftUI apps by using it in view models or environments to manage settings, but it doesn't provide direct property wrappers like @AppStorage, so some wiring is required.

Question 4

How to handle data migration when changing custom types in TypedDefaults?

Accepted Answer

You need to implement custom logic in the init?(_ object:) method to handle legacy data formats, as the library doesn't offer built-in versioning or migration tools, which can be error-prone.

Question 5

What are the performance implications of using TypedDefaults?

Accepted Answer

Performance is similar to native NSUserDefaults since it wraps standard calls, but serialization and deserialization of complex types might introduce overhead if not optimized, especially for large or nested structures.

Question 6

Does TypedDefaults support storing arrays of custom types?

Accepted Answer

Yes, but you must ensure array elements conform to DefaultsConvertible and handle serialization in the parent type's methods, which can add complexity for nested data structures.

TypedDefaults

What is TypedDefaults?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions