✅ Vertical Slice Architecture and Shared Code?
I've adapted one of my projects from using the more traditional Clean Architecture and Repositories/services, but what happens if you have logic that is used across multiple features, if VSA is against using something like a service, do you just repeat code where you need to? That seems silly to me.
But for example say you have a LoginCommandHandler and RefreshTokensCommandHandler, both would have logic for generating both an access and refresh token, so how would you go about handling that? I current still have several "services" in project for things like Tokens and Email for occasions where I know something is going to be reused in multiple features, an I'm not sure if they should be changed
But for example say you have a LoginCommandHandler and RefreshTokensCommandHandler, both would have logic for generating both an access and refresh token, so how would you go about handling that? I current still have several "services" in project for things like Tokens and Email for occasions where I know something is going to be reused in multiple features, an I'm not sure if they should be changed
