Documenting Apple's undocumented and unclear code. Last month I encountered my first need for a custom CoreData merge policy and turned to the Apple documentation for guidance. There wasn't much and I was getting a weird crash that made no sense to me.…
Quite frequently I find myself needing to import a module to gain access to a type (usually a model), but I never interact with that module again. Recently I discovered simple way to skip having to put import ModuleName at the top of my code. This trick is especially handy…
Have you noticed that all the examples on Apple's website and elsewhere only use List views for the sidebar and don't have a NavigationStack in the final detail view that they push additional content onto? There's a reason for that, and unfortunately it's not a pleasant one.…
