SwiftUI中基于Combine与MVVM的ViewModel与View通信方案咨询
解决方案
1 修正PassthroughSubject订阅方式(推荐)
你之前的PassthroughSubject方案本身是最符合需求的,问题出在订阅语法错误:onReceive可以直接接收任意Publisher作为参数,不需要加$符号,$仅用于访问@Published属性的投影Publisher,普通PassthroughSubject本身就是Publisher,直接传入即可。
实现代码
ViewModel层
首先定义页面专属的事件枚举,在ViewModel中声明PassthroughSubject,无需@Published修饰:
class ForgotPasswordViewModel: ObservableObject { // 定义页面所有事件类型 enum Event { case passwordResetSuccess case apiError(Error) case requestInProgress } @Published var username: String = "" // 事件流,不存储当前值,发送即销毁 let events = PassthroughSubject<Event, Never>() private var passwordApi = Api<Response<Success>>() private var cancellables = Set<AnyCancellable>() init() { self.passwordApi.$status .receive(on: DispatchQueue.main) .sink { [weak self] result in guard let self = self, let result = result else { return } switch result { case .inProgress: self.events.send(.requestInProgress) case .success(_): self.events.send(.passwordResetSuccess) case .failed(let error): self.events.send(.apiError(error)) } } .store(in: &cancellables) } }
View层
直接订阅events属性即可,无需额外处理状态清空:
struct ForgotPasswordView: View { @Environment(\.presentationMode) var presentationMode @StateObject private var viewModel = ForgotPasswordViewModel() // 注入全局toast协调器 @EnvironmentObject var toastCoordinator: ToastCoordinator var body: some View { NavigationView { // 页面内容省略 } .onReceive(viewModel.events) { event in switch event { case .passwordResetSuccess: presentationMode.wrappedValue.dismiss() toastCoordinator.show(.success("密码重置成功")) case .apiError(let error): toastCoordinator.show(.error(error.localizedDescription)) case .requestInProgress: // 处理加载状态,比如展示loading break } } } }
这个方案完全避免了冗余状态变量和手动清空的问题,所有事件逻辑收敛在ViewModel中,View仅负责响应事件做UI操作,符合MVVM的职责拆分,且单元测试非常方便:直接订阅ViewModel的events属性即可验证事件触发逻辑是否正确。
2 闭包回调方案(适合简单页面)
如果页面事件数量少于3个,还可以用更轻量的闭包回调方案,不需要引入Combine相关代码:
ViewModel层
class ForgotPasswordViewModel: ObservableObject { @Published var username: String = "" // 事件回调属性 var onSuccess: (() -> Void)? var onError: ((Error) -> Void)? private var passwordApi = Api<Response<Success>>() private var cancellables = Set<AnyCancellable>() init() { self.passwordApi.$status .receive(on: DispatchQueue.main) .sink { [weak self] result in guard let self = self, let result = result else { return } switch result { case .success(_): self.onSuccess?() case .failed(let error): self.onError?(error) default: break } } .store(in: &cancellables) } }
View层
在onAppear中给ViewModel的回调赋值即可:
struct ForgotPasswordView: View { @Environment(\.presentationMode) var presentationMode @StateObject private var viewModel = ForgotPasswordViewModel() @EnvironmentObject var toastCoordinator: ToastCoordinator var body: some View { NavigationView { // 页面内容省略 } .onAppear { viewModel.onSuccess = { [weak self] in self?.presentationMode.wrappedValue.dismiss() toastCoordinator.show(.success("密码重置成功")) } viewModel.onError = { error in toastCoordinator.show(.error(error.localizedDescription)) } } } }
方案选型建议
- 页面事件多、逻辑复杂的场景优先选PassthroughSubject+事件枚举方案,扩展性更强,所有事件统一管理,便于后续维护
- 简单页面、事件少的场景选闭包回调方案,代码更轻量化,学习成本更低
内容的提问来源于stack exchange,提问作者Eli
相关产品推荐
相关产品推荐

