rhonabwy | Javascript Object Signing and Encryption | Authentication library

I am still in the process of learning to utilize SwiftUI patterns in the most optimal way. But most SwiftUI MVVM implementation examples I find are very simplistic. They usually have one database class and then 1-2 viewmodels that take data from there and then you have views.

In my app, I have a SQLite DB, Firebase and different areas of content. So I have a few separate model-vm-view paths. In the Android equivalent of my app, I used a pattern like this:

View - ViewModel - Repository - Database

This way I can separate DB logic like all SQL queries in the repository classes and have the VM handle only view related logic. So the whole thing looks something like this:

In Android this works fine, because I just pass through the LiveData object to the view. But when trying this pattern in SwiftUI, I kind of hit a wall:

1. It doesn't work / I don't know how to correctly connect the Published objects of both
2. The idea of "chaining" or nesting ObservableObjects seems to be frowned upon:

This article about Nested Observable Objects in SwiftUI:

I’ve seen this pattern described as “nested observable objects”, and it’s a subtle quirk of SwiftUI and how the Combine ObservableObject protocol works that can be surprising. You can work around this, and get your view updating with some tweaks to the top level object, but I’m not sure that I’d suggest this as a good practice. When you hit this pattern, it’s a good time to step back and look at the bigger picture.

So it seems like one is being pushed towards using the simpler pattern of:

View - ViewModel - Database Repository

Without the repository in-between. But this seems annoying to me, it would make my viewmodel classes bloated and would mix UI/business code with SQL queries.

So this is a simplified version of my code to demonstrate the problem:

Repository: