Swift中如何用Reduce/FlatMap将嵌套消息转为单一Message数组？

Yes, you absolutely can use a combination of recursion and either reduce or flatMap to flatten the nested MessageServer structure into a single array of Message objects. Here's a step-by-step approach to make this work:

Step 1: Create a Recursive Helper Function #

First, you need a helper that converts a MessageServer (including all its nested children) into a flat array of Message instances. This uses recursion to handle nested messages:

func flattenMessageServer(_ serverMsg: MessageServer, currentUserID: String) -> [Message] {
    // Convert the current server message to your app's Message type
    let currentMessage = Message(
        message: serverMsg.message,
        createdDate: serverMsg.createdDate,
        displayName: serverMsg.user.displayName, // Assume User has this property
        isMine: serverMsg.user.id == currentUserID, // Compare user ID to current user
        attachments: serverMsg.attachments.map { File(from: $0) } // Map FileServer to File
    )
    
    // Option 1: Use flatMap to recursively flatten child messages
    let childMessages = serverMsg.messages.flatMap { flattenMessageServer($0, currentUserID: currentUserID) }
    
    // Option 2: Use reduce instead of flatMap (same end result)
    // let childMessages = serverMsg.messages.reduce([]) { $0 + flattenMessageServer($1, currentUserID: currentUserID) }
    
    // Combine current message with all child messages (top-level first)
    return [currentMessage] + childMessages
}

Step 2: Integrate with Your Observable Pipeline #

Now update your getMessages function to use this helper. Note: I’m assuming messageServiceEndpoints.getMessages(for: id) returns an Observable<MessageServer> (matching your JSON example of a single top-level message):

func getMessages(sectionID id: String, currentUserID: String) -> Observable<[Message]> {
    return messageServiceEndpoints
        .getMessages(for: id)
        .map { flattenMessageServer($0, currentUserID: currentUserID) }
}

If your endpoint returns an Observable<[MessageServer]> instead, adjust it to flatten each item and collect into an array:

func getMessages(sectionID id: String, currentUserID: String) -> Observable<[Message]> {
    return messageServiceEndpoints
        .getMessages(for: id)
        .flatMap { Observable.from($0) } // Emit each MessageServer individually
        .flatMap { Observable.from(flattenMessageServer($0, currentUserID: currentUserID)) } // Flatten each nested structure
        .toArray() // Collect all Messages into a single array
}

Key Details to Note #

• Recursion: This ensures we handle any depth of nested messages, not just the first level.
• isMine Logic: You’ll need access to the current user’s ID to set this flag—pass it into the helper function as shown.
• Attachment Mapping: Make sure you have a way to convert FileServer to your app’s File type (I used a hypothetical convenience initializer here).
• Top-Level First: The helper adds the current message first, so the top-level message will always be the first item in the final array, which matches your UI requirement.

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