Add checkout handling #66
Conversation
| self?.state.onNext(.error(error: error)) | ||
| } | ||
| if let success = success, success == true { | ||
| // TODO: |
There was a problem hiding this comment.
It would be implemented after checkout flow changes
| @@ -12,4 +12,8 @@ struct CartProductListUseCase { | |||
| public func getCartProductList(_ callback: @escaping RepoCallback<[CartProduct]>) { | |||
| Repository.shared.getCartProductList(callback: callback) | |||
| } | |||
|
|
|||
| public func clearCart(_ callback: @escaping RepoCallback<Bool>) { | |||
There was a problem hiding this comment.
You need to create separate use case (ClearCartUseCase) and move this method to them because we use simple rule: one use case = one action. Also I see that we have many different methods in CheckoutUseCase. I think we also need to separate them. @plzen Am I right?
There was a problem hiding this comment.
It's better to have use cases small as possible. So we need to encapsulate some action to use case. I agree that we need to split CheckoutUseCase.
| @@ -12,4 +12,8 @@ struct CartProductListUseCase { | |||
| public func getCartProductList(_ callback: @escaping RepoCallback<[CartProduct]>) { | |||
| Repository.shared.getCartProductList(callback: callback) | |||
| } | |||
|
|
|||
| public func clearCart(_ callback: @escaping RepoCallback<Bool>) { | |||
There was a problem hiding this comment.
It's better to have use cases small as possible. So we need to encapsulate some action to use case. I agree that we need to split CheckoutUseCase.
Add checkout success screen.
Add cart clearing.
Add dev scheme.