Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Or put in another way, would it be suggested to have separate stack (context, model, coordinator) for different context? what’s the pros and cons of separating them, and what’s the pros and cons of having different context share the same model and coordinator?
Yes, it is quite acceptable for multiple contexts to share the same coordinator, model, etc. It’s a very common usage pattern.
Since you didn’t say why you thought it might not be, or what problems you’re running into (if any), I’ll just leave it at that.