-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: implement customer and account creation #14
Conversation
...lin/io/holixon/cqrshexagonaldemo/demoparent/transactions/application/CreateAccountUsecase.kt
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, the @Component
annotation can be removed and the event publisher could be wrappen in an adapter.
Should we take advantage of extension functions to build our entities or DTO's ? i see some advantages to do that approach because we have cleaner Code, readability. On the other hand with class component we have better isolation flexibility. Do you think its worth to discuss this ? |
refactor: use custom annotations for usecases and services feat: add customer creation methods
Its always worth discussing, but I need it a little bit more precise: in what spots would you like to use extension functions? |
Refactor: Change flyway configuration to support jdbc database Refactor: Update dependencies to support mySql
…aving entity. Refactor: Change jdbc connection to mySql
…onal into 13-create-an-account # Conflicts: # pom.xml
No description provided.