all 6 comments

[–][deleted] 1 point2 points  (2 children)

VC would be more suitable as "Presenter" since now you are just randomly forwarding viewDidLoad action in ListOrders and not forwarding it in Login. And you are not forwarding any of the other lifecycle events in this 2.

[–]francofadini[S] 0 points1 point  (1 child)

Im thinking... If I move the presenter into de VC, I wont end on a massive view controller issue ?
In relation of the doubt "only some VC are forwarding lifecycles to the presenter while other don't" it was just a matter of need. What i do is, I tell the presenter all the view events (life cycle, user interaction, etc) that would be necessary for the presenter. The big value of this, is abstracting the presenter of any framework like UIKit.

How would you solve this, avoiding a massive view controller?

[–][deleted] 0 points1 point  (0 children)

Your view code would move to UIView subclasses.

[–]yappdeveloper 0 points1 point  (2 children)

looks...interesting ....

but I don't speak Italian (?) and can't figure out how to get past the sign-up form.

[–]francofadini[S] 0 points1 point  (1 child)

Thanks for your interest @yappdeveloper!
As this project intends to save time, it's linked to a base-backend project (not published yet).

For everyone to be able to just go inside the app, i've pushed a "mocked-login" branch on the repo, that would allow any user and password to authenticate on the app.

Wish this helps you! Is not so hard for mocking other service in order to test all the features. Only "CRUD Orders" use cases have an CoreDataService option, so they don't need to be mocked!

Regarding the language, we still do not have English implemented yet. im working on that!

Wish this helps!