Fixer of explicitly unwrapped optionals

Filtering by Tag: Documentation

Some extra Documentation on NSPersistentCloudKitContainer is needed about simulators and devices

Added on by Paul Wood.

This page of Documentation should have a warning saying that a physical device is required to test the automatic syncing of NSPersistentCloudKitContainer

On the page, Mirroring a Core Data Store with CloudKit I can read in the section “Set Up Your Development Environment” A sentence reads “You can run and test Core Data with CloudKit apps using Simulator. You may also test with multiple physical devices logged into the same iCloud account on a good wireless internet connection.” But no explicit warning that the simulator will not have the same experience as a physical device because it does not receive push notifications.

On this page, Synchronizing a Local Store to the Cloud in the Section “Configure the Sample Code Project” a note about using physical devices should be included to see the automatic “live” syncing using push notifications

I had to learn about this via a blog post by Andrew C Bancroft.

I can’t wait to use this feature in iOS 13. Its a great addition to the frameworks and removes a lot of friction of working with CloudKit and CoreData

Combine needs back pressure documentation

Added on by Paul Wood.

For context to this post, Heres some of us talking about it on Twitter:

This lack of documentation will quickly lead to performance issues being the default for many new to the concept of Reactive programming. An overview of back-pressure in Combine should be written and linked to from this page covering Combine in General:

Demand isn’t even mentioned on this page of Documentation about Subject.

Demand and how it works could be better explained on this page on Subscribers are the source of truth for demand:

The returned value for demand should be documented on these pages:

CurrentValueSubject and PassthroughSubject are implemented with demand unlimited. I assume this is because they must conform to both a publisher as well as a subscriber. This really should be explained in their documentation to prevent people from using them to implement back pressure and sharing the results to other subscribers using .share()

Need some inspiration on how to start documenting the overall subject? Please look at my personal mental model on back pressure here. With many more links of inspiration, for example RxJava’s documentation, are in the post.