After using this code organization for a while, I often get circular dependency issues. so I reorganized the code structure like this https://github.com/nurcahyaari/coma/tree/main/src.

the module is placed inside the application package, where all of the contract (service interface or repository interface) and the domain-related logic (entity, value object) are placed inside the domain package.

Despite this, the dependency issues still exist while importing other packages if the request and the response are a dto, so that I will change the parameters and the response as an entity. but I know it's broken the dto pattern.

Or maybe I could move the DTO to the domain package, but I don't know is it okay or not