Steven Sorial

Facing the same issue, especially with the Lossy.. wrappers.

@Strobocop I have this extension in my code ```swift extension KeyedDecodingContainer { func decodeRawKeyedDict( _ type: [K: V].Type, forKey key: Key ) throws -> [K: V] where K.RawValue: Decodable &...

Changed it so each `DefaultsAdapter` has its own syncer. Edit: This change supports use cases where there are multiple `DefaultsAdapter`s in the same app. This has one caveat where if...

Got `PartialKeyPath` working 🎉🎉 It was a Swift type inference bug. [SR-5667](https://bugs.swift.org/browse/SR-5667) - [forums](https://forums.swift.org/t/array-of-partialkeypath-t-ambiguous/16231/2) Usage: ```swift // Prefs.swift extension DefaultsKeys { var username: DefaultsKey { return .init("username") } var launchCount:...

@sunshinejr Thanks for the reply > * add checks on watchOS (since the `NSUbiquitousKeyValueStore` is not available on watchOS) Done. > * add some tests for syncing? I'm having a...

hey @sunshinejr, I think I'm done with this PR. I tried different approaches for testing with no luck. I hope this feature will get implemented one day 🙏, either building...

Implement `init(from decoder: Decoder)` in `UserConfig` to override the default decoding behavior.

Great :) > if it's possible to have with how we structured the API nowadays. That's actually was going to be my next question 😄 - is it even possible...

> the global `Defaults` variable would use `UserDefaults.standard` as a provider as it is currently (and people that choose to use the cloud-kit backing could just override it) @sunshinejr actually...

actually no, but I'm sure it will be needed by others because the whole synced container has a 1 MB limit, so some users will have to keep larger keys...