Helps you define secure storages for your properties using Swift property wrappers.
🌟 Features
All keys are hashed using SHA512 and all values are encrypted using AES-GCM to keep user information safe, automagically.
Symmetric key is stored in Keychain in a totally secure way.
🐒 Basic usage
@UserDefault
This property wrapper will store your property in UserDefaults using StoreKey (any String but i recommend you a String typed enum).
Optionally, you can assign a default value to the property that will be secure stored at initialization.
@UserDefault(<#StoreKey#>)
var yourProperty: YourType? = yourDefaultValueIfNeeded
UserDefaultsStorage is also available, a subclass of UserDefaults with all the security provided by this library, where you can customize suite name.
@Keychain
This property wrapper will store your property in Keychain using StoreKey.
@Keychain(<#StoreKey#>)
var yourProperty: YourType? = yourDefaultValueIfNeeded
As UserDefaultsStorage, KeychainStorage is also available, where you can customize access, group and synchronize it with iCloud.
@Singleton
This property wrapper will store your property in a memory singleton, every property with the same wrapper and key can access or modify the value from wherever it is.
@Singleton(<#StoreKey#>)
var yourProperty: YourType? = yourDefaultValueIfNeeded
This property wrapper is similar to @Singleton but, together with @Register, will inject your dependencies. More details in Dependency Injection usage guide.
@Inject
var yourDependency: YourProtocol?
As SingletonStorage, InjectStorage is also available.
@Store
This is a custom wrapper, you can define your own Storage protocol implementation.
@Store(<#YourStorage#>, <#StoreKey#>)
var yourProperty: YourType? = yourDefaultValueIfNeeded
As InjectStorage, DelegatedStorage is also available with all the magic of this library.
🧙♂️ Codable usage
If your property conforms Codable protocol, just add Codable keyword as prefix of your property wrapper.
@CodableUserDefault
@CodableKeychain
@CodableSingleton
@CodableStore
🥡 Unwrapped usage
To avoid continually unwrapping your property, just add Unwrapped keyword as prefix of your property wrapper, assign a default value (mandatory except for @UnwrappedInject), and it will return stored value or default value, but your property will always be there for you.
@UnwrappedUserDefault
@UnwrappedKeychain
@UnwrappedSingleton
@UnwrappedInject
@UnwrappedStore
🥡 + 🧙♂️ Combo usage
You can also combine previous cases in case you need it, unwrapped first please.
@UnwrappedCodableUserDefault
@UnwrappedCodableKeychain
@UnwrappedCodableSingleton
@UnwrappedCodableStore
💉 Dependency Injection usage
@Register (click to expand)
This property wrapper will register the implementations of your dependencies.
Register them wherever you want before inject it, but be sure to do it only once (except if you use qualifiers), for example, in an Injector class.
You can register through a protocol or directly using your class implementation.
@Register
var yourDependency: YourProtocol = YourImplementation()
@Register
var yourDependency = YourImplementation()
You can also define a closure that builds your dependency.
Just remember cast your dependency if you are going to inject it through a protocol.
@Register
var yourDependency = {
YourImplementation() as YourProtocol
}
@Register
var yourDependency = {
YourImplementation()
}
You can also register your dependencies only after the moment someone tries to inject them and you haven’t registered them yet,
for this you can use the error closure.
InjectStorage.standard.errorClosure = { error in
if case InjectError.notFound = error {
YourImplementation.register()
}
}
You can get this syntactic sugar because you can now use property wrappers in function parameters.
These property wrappers injects your dependencies @Register implementations.
@Inject
var yourDependency: YourProtocol?
@Inject
var yourDependency: YourImplementation?
@UnwrappedInject
var yourUnwrappedDependency: YourProtocol
@UnwrappedInject
var yourUnwrappedDependency: YourImplementation
Scope
Because these property wrappers works similarly to @Singleton, the default scope is .singleton, but if you use builder closures on @Register, you can modify them to inject a single instance.
@Inject(.instance)
var yourDependency: YourProtocol?
@UnwrappedInject(.instance)
var yourUnwrappedDependency: YourProtocol
@InjectWith and @UnwrappedInjectWith (click to expand)
Your dependency may need parameters when injecting, you can pass them with these property wrappers.
Simply define a model with your dependency parameters and pass it.
It will inject a new instance built with these parameters.
@Register
var yourDependency = { parameters in
YourImplementation(parameters) as YourProtocol
}
@Inject(YourParameters())
var yourDependency: YourProtocol?
@UnwrappedInject(YourParameters())
var yourUnwrappedDependency: YourProtocol
Qualifiers (click to expand)
You can use qualifiers to provide various implementations of a particular dependency. A qualifier is just a @objc protocol that you apply to a class.
For example, you could declare Dog and Cat qualifier protocols and apply it to another class that conforms Animal protocol. To declare this qualifier, use the following code:
You can then define multiple classes that conforms Animal protocol and uses this qualifiers:
class DogImplementation: Animal, Dog {
func sound() { print("Woof!") }
}
class CatImplementation: Animal, Cat {
func sound() { print("Meow!") }
}
Both implementations of the class can now be @Register:
@Register
var registerDog: Animal = DogImplementation()
@Register
var registerCat: Animal = CatImplementation()
To inject one or the other implementation, simply add the qualifier(s) to your @Inject:
@UnwrappedInject(Dog.self)
var dog: Animal
@UnwrappedInject(Cat.self)
var cat: Animal
dog.sound() // prints Woof!
cat.sound() // prints Meow!
Testing (click to expand)
One of the advantages of dependency injection is that the code can be easily testable with mock implementation.
That is why there is a Mock qualifier that has priority over all, so you can have your dependencies defined in the app and create your mock in the test target simply by adding this qualifier.
// App target
class YourImplementation: YourProtocol {}
@Register
var yourDependency: YourProtocol = YourImplementation()
@Inject
var yourDependency: YourProtocol?
// Test target
class YourMock: YourProtocol, Mock {}
@Register
var yourDependency: YourProtocol = YourMock()
Groups (click to expand)
When you have a lot of dependencies in your app, you may want to optimize dependency resolution.
You can group them using @Register(group:) and a DependencyGroupKey:
@Register(group: <#DependencyGroupKey#>)
var yourDependency: YourProtocol = YourImplementation()
@Inject(group:) will look for those dependencies only in that group:
@Inject(group: <#DependencyGroupKey#>)
var yourDependency: YourProtocol?
👀 Examples
Talk is cheap. Show me the code.
// Securely stored in UserDefaults.
@UserDefault("username")
var username: String?
// Securely stored in Keychain.
@Keychain("password")
var password: String?
// Securely stored in a Singleton storage.
@Singleton("sessionToken")
var sessionToken: String?
// Securely stored in a Singleton storage.
// Always has a value, the stored or the default.
@UnwrappedSingleton("refreshToken")
var refreshToken: String = "B0610306-A33F"
struct User: Codable {
let username: String
let password: String?
let sessionToken: String?
}
// Codable model securely stored in UserDefaults.
@CodableUserDefault("user")
var user: User?
🛠 Compatibility
macOS 10.15+
iOS 13.0+
iPadOS 13.0+
tvOS 13.0+
watchOS 6.0+
⚙️ Installation
You can use the Swift Package Manager by declaring SecurePropertyStorage as a dependency in your Package.swift file:
🔐 Secure Property Storage
🌟 Features
All keys are hashed using SHA512 and all values are encrypted using AES-GCM to keep user information safe, automagically. Symmetric key is stored in Keychain in a totally secure way.
🐒 Basic usage
@UserDefault
This property wrapper will store your property in UserDefaults using
StoreKey
(anyString
but i recommend you a String typed enum). Optionally, you can assign a default value to the property that will be secure stored at initialization.UserDefaultsStorage
is also available, a subclass ofUserDefaults
with all the security provided by this library, where you can customize suite name.@Keychain
This property wrapper will store your property in Keychain using
StoreKey
.As
UserDefaultsStorage
,KeychainStorage
is also available, where you can customize access, group and synchronize it with iCloud.@Singleton
This property wrapper will store your property in a memory singleton, every property with the same wrapper and key can access or modify the value from wherever it is.
As
KeychainStorage
,SingletonStorage
is also available.@Inject
This property wrapper is similar to
@Singleton
but, together with@Register
, will inject your dependencies. More details in Dependency Injection usage guide.As
SingletonStorage
,InjectStorage
is also available.@Store
This is a custom wrapper, you can define your own
Storage
protocol implementation.As
InjectStorage
,DelegatedStorage
is also available with all the magic of this library.🧙♂️ Codable usage
If your property conforms
Codable
protocol, just addCodable
keyword as prefix of your property wrapper.🥡 Unwrapped usage
To avoid continually unwrapping your property, just add
Unwrapped
keyword as prefix of your property wrapper, assign a default value (mandatory except for@UnwrappedInject
), and it will return stored value or default value, but your property will always be there for you.🥡 + 🧙♂️ Combo usage
You can also combine previous cases in case you need it, unwrapped first please.
💉 Dependency Injection usage
@Register (click to expand)
This property wrapper will register the implementations of your dependencies. Register them wherever you want before inject it, but be sure to do it only once (except if you use qualifiers), for example, in an
Injector
class. You can register through a protocol or directly using your class implementation.You can also define a closure that builds your dependency. Just remember cast your dependency if you are going to inject it through a protocol.
You can also register your dependencies only after the moment someone tries to inject them and you haven’t registered them yet, for this you can use the error closure.
You can get this syntactic sugar because you can now use property wrappers in function parameters.
@Inject and @UnwrappedInject (click to expand)
These property wrappers injects your dependencies
@Register
implementations.Scope
Because these property wrappers works similarly to
@Singleton
, the default scope is.singleton
, but if you use builder closures on@Register
, you can modify them to inject a single instance.@InjectWith and @UnwrappedInjectWith (click to expand)
Your dependency may need parameters when injecting, you can pass them with these property wrappers. Simply define a model with your dependency parameters and pass it. It will inject a new instance built with these parameters.
Qualifiers (click to expand)
You can use qualifiers to provide various implementations of a particular dependency. A qualifier is just a
@objc protocol
that you apply to aclass
.For example, you could declare
Dog
andCat
qualifier protocols and apply it to another class that conformsAnimal
protocol. To declare this qualifier, use the following code:You can then define multiple classes that conforms
Animal
protocol and uses this qualifiers:Both implementations of the class can now be
@Register
:To inject one or the other implementation, simply add the qualifier(s) to your
@Inject
:Testing (click to expand)
One of the advantages of dependency injection is that the code can be easily testable with mock implementation. That is why there is a
Mock
qualifier that has priority over all, so you can have your dependencies defined in the app and create your mock in the test target simply by adding this qualifier.Groups (click to expand)
When you have a lot of dependencies in your app, you may want to optimize dependency resolution.
You can group them using
@Register(group:)
and aDependencyGroupKey
:@Inject(group:)
will look for those dependencies only in that group:👀 Examples
🛠 Compatibility
⚙️ Installation
You can use the Swift Package Manager by declaring SecurePropertyStorage as a dependency in your
Package.swift
file:By default, all property wrappers are installed and you can
import
them, but if you want, you can install only some of them:For more information, see the Swift Package Manager documentation.
Or you can use Carthage:
🍻 Etc.
👨💻 Author
Alex Rupérez – @alexruperez – me@alexruperez.com
👮♂️ License
SecurePropertyStorage is available under the MIT license. See the LICENSE file for more info.