Coordinator - some questions only about coordinator-example HOT 2 OPEN

Business logic should not be in the View Controllers or the Coordinators, it should be further down in either a business service layer or in the business domain objects.

You may see simple examples with business rules closer to the UI, but that’s more likely a symptom of the example trying to keep it simple by avoiding all the infrastructure typical of a larger app.

from coordinator-example.

I'm implementing a test project just to get a feel for how it works. And I'm at a page where I'd like to skip a VC in the flow similar to in the example app you had in the blog.

The example goes like

didEnterEmail:email
   if email contains "example.com"
       showCompleted
   else
       showEmailIsBlocked

But the decision to have the email blocked would be a business logic decision, thus not supposed to be in this coordinator class. So in this case what would be an appropriate way to decide on the flow? I'm leaning towards some form of "Email wrapper" model object that contains a method "isValidForRegisrationFlow", or similar but I'm not sure if it is a good idea.

Or possibly a model object specifically for the flow, that in turn contains this logic (including same logic for other steps, such as e.g. name/pwd validation/etc).

Sorry for the unsolicited questions

from coordinator-example.