PlayerRequest.swift is identical in GRDBAsyncDemo and GRDBCombineDemo about grdb.swift HOT 4 CLOSED

The next version of the lib will not mention async sequences in the README of GRDBAsyncDemo.

Thank you for the report, @hjrnunes!

from grdb.swift.

Hello @hjrnunes,

Oh, I suppose you're surprised because there is no async sequence in GRDBAsyncDemo.

Thank you for reporting this: I'll update my wording, so that it is less misleading.

I did try to build a SwiftUI app from the ValueObservation.values(in:) async sequence.

Unfortunately, there is no way to tell Swift Concurrency to start an async sequence synchronously, which means that a SwiftUI view that feeds from an async sequence MUST display an empty state until the first value is produced. While some apps can live with this, some other apps can not. That's why the GRDBAsyncDemo demo is still Combine-based for the database observation feature. Combine has no problem starting a publisher synchronously, and is a better fit than Swift Concurrency for the most demanding UI applications.

If you really want to use an async sequence, there's no problem: start a Task, and iterate the values returned by ValueObservation.values(in:). There's no demo for that, but nothing prevents you from doing it. Your view will have to display an empty state, until the first value is produced by the Swift Concurrency runtime.

from grdb.swift.

Thanks @groue

from grdb.swift.

The doc was updated in the new version v6.27.0. Thanks again!

from grdb.swift.