SwiftUI中BindableObject传递及子视图绑定Message的技术疑问

Great question—this is a common point of confusion when working with SwiftUI's data flow, especially for list items that need to update a source of truth in a BindableObject. Let's break this down clearly.

First: Why your direct @Binding attempt failed #

The core issue here is that Message is a value type (a struct). When you tried passing a @Binding<Message> directly, you were actually binding to a copy of the message from the messagesList array, not the original instance stored in MessageStore. Any changes you made to this copy wouldn't propagate back to the array in the BindableObject, hence no UI updates. That's why your approach didn't work.

Is the "BindableObject + index" approach reasonable? #

Yes, the method shown in Apple's tutorial is technically valid—it works because you're directly modifying the array in the BindableObject (the single source of truth), which triggers the didChange publisher to update the UI. However, it's definitely not the most clean or concise approach, especially with the forced unwrap for the index (which could crash if the message isn't found).

Better alternatives: Pass only the necessary binding #

You absolutely can avoid passing the entire BindableObject to child views. Here are two cleaner approaches:

1. Pass a binding to the specific list item directly #

Instead of passing the Message struct and then looking up its index in the child view, pass a Binding<Message> from the parent view by accessing the array element directly.

Updated MessagesView:

struct MessagesView : View {
    @EnvironmentObject var messageStore: MessageStore
    var body: some View {
        NavigationView {
            // Use enumerated() to get both index and message
            List(Array(messageStore.messagesList.enumerated()), id: \.element.id) { index, message in
                NavigationButton(destination: Text(message.id)) {
                    // Pass the binding to the specific array element
                    MessageRow(message: self.$messageStore.messagesList[index])
                }
            }
            .navigationBarTitle(Text("Messages"))
        }
    }
}

Simplified MessageRow:

struct MessageRow: View {
    // Now we only need the binding to the single Message
    @Binding var message: Message
    var body: some View {
        Toggle(isOn: $message.toggle) {
            Text("Test toggle")
        }
    }
}

This way, MessageRow doesn't need to know about MessageStore at all—it just works with the specific message binding it receives.

2. Add a helper method to BindableObject for bindings #

If you prefer not to handle indexes in your view, you can add a method to MessageStore that returns a Binding<Message> for a specific message ID. This encapsulates the index lookup logic in the data store instead of the view.

Updated MessageStore:

class MessageStore: BindableObject {
    let didChange = PassthroughSubject<MessageStore, Never>()
    var messagesList: [Message] = testData {
        didSet {
            didChange.send(self)
        }
    }
    
    // Helper method to get a binding for a message by ID
    func bindingForMessage(withId id: String) -> Binding<Message> {
        Binding(
            get: {
                // Force unwrap is okay here if you're sure the ID exists
                self.messagesList.first(where: { $0.id == id })!
            },
            set: { newMessage in
                guard let index = self.messagesList.firstIndex(where: { $0.id == id }) else { return }
                self.messagesList[index] = newMessage
            }
        )
    }
}

Usage in MessagesView:

List(messageStore.messagesList) { message in
    NavigationButton(destination: Text(message.id)) {
        MessageRow(message: self.messageStore.bindingForMessage(withId: message.id))
    }
}

The MessageRow stays the same as in the first alternative—still only needing a @Binding var message: Message.

Key Takeaway #

SwiftUI's data flow relies on having a single source of truth (your BindableObject), but you don't need to pass the entire object to every child view. By passing targeted bindings to individual list items, you keep your views focused and avoid unnecessary dependencies on the full data store.

内容的提问来源于stack exchange，提问作者DenFav