You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -315,15 +315,15 @@ If you use the Dependency Injection approach described above you can easily mock
315
315
simulate, like a long taking webservice request or a full database.
316
316
317
317
## Troubleshooting
318
-
0. I can not register my Interactor at the InteractorExecuter. I get a Compiler Error.
319
-
* Make sure the `interactor` implements the `Interactor` protocol
320
-
* Make sure the `request` is a subclass of `InteractorRequest<Response>` and is correctly typed.
321
-
* Make sure the `request` is an initialized object instance.
322
-
323
-
0. Calling execute on the InteractorExecuter does not call the execute method of my Interactor.
324
-
* Make sure you have registered the Interactor with the corresponding InteractoRequest by calling the `registerInteractor()` function on the `InteractorExecuter`.
325
-
* Make sure you have called the `registerInteractor()` and the `execute()` function on the **same** instance of `InteractorExecuter`.
326
-
* Make sure you have set an `onError` closure on the `request`. It might provide additional details in the error message about what went wrong.
318
+
1. I can not register my Interactor at the InteractorExecuter. I get a Compiler Error.
319
+
* Make sure the `interactor` implements the `Interactor` protocol
320
+
* Make sure the `request` is a subclass of `InteractorRequest<Response>` and is correctly typed.
321
+
* Make sure the `request` is an initialized object instance.
322
+
323
+
1. Calling execute on the InteractorExecuter does not call the execute method of my Interactor.
324
+
* Make sure you have registered the Interactor with the corresponding InteractoRequest by calling the `registerInteractor()` function on the `InteractorExecuter`.
325
+
* Make sure you have called the `registerInteractor()` and the `execute()` function on the **same** instance of `InteractorExecuter`.
326
+
* Make sure you have set an `onError` closure on the `request`. It might provide additional details in the error message about what went wrong.
327
327
328
328
## Credits
329
329
Special thanks from [Florian Rieger](https://github.com/florieger) to the people that helped getting ACInteractor together.
0 commit comments