-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION] How to avoid duplicate interactor #4
Comments
Hi Hung The easiest thing you can do is extract the DoesPostEsisted class to a common package and reuse it from both use cases. I don't see anything wrong with it, as it sounds like it's part of your business logic. I hope this answer your questions |
Thank you so much for your comment. Example:
Edit: Thanks, |
yes, that's what I mean. There's nothing wrong in extracting duplicate code, as long as you still respected the fact that in core we only want business logic. Not sure what you mean by boundaries vs interactors though? Mattia |
I'm confusing, Boundaries are interface, Interactors are Usecases. Thank you for supporting, I really appreciate it. Have a good day! |
Hello,
What if I create a new use case, like getSomething, and use the same DoesExchangeExist class.
Should I use this class or create new class for new use case?
Thanks in advance!
Best regards,
Huka
The text was updated successfully, but these errors were encountered: