Dynamic Lists With SwiftUI Using Swift Concurrency for Asynchronous Data Loading

In a previous blog post, I described an implementation of lists in SwiftUI where items are loaded dynamically as the user scrolls and additional data for each item is fetched asynchronously. I also wanted to provide a reusable infrastructure for lists where you could concentrate only on the data fetching logic and the presentation of a single list item, but didn’t quite reach that goal.

In this blog post, I try to improve the list infrastructure and the separation of concerns between the data model and UI. I also want to test the Swift Concurrency features (async/await etc) for the asynchronous parts, and see how well it plays with SwiftUI.

Functional Increments in Web Services

Functional Increments in Web Services

Have you seen code reviews where the code being added is not yet used anywhere in a web service? It's not yet covered with automated tests? It will likely be refactored or deleted in a subsequent pull request (aka PR)? Is a library that is not or only partially used? All of these cases represent non-functional increments to a web service.

A functional increment contains only code that is being used by the service to achieve some functionality. Such code is typically fully covered with automated tests. A functional increment should also be self-contained in a way that it doesn't rely on future changes to expose functionality.