Create a Volo.Abp.Ddd.Domain.Shared package.

[maliming]

No description provided.

[hikalkan]

@maliming can you plaese explain why we need it and what that package will include?

[maliming]

Similar to Volo.Abp.Ddd.Application.Contracts, It will include the interfaces and constants.

Someone told me the Volo.Abp.Ddd.Domain package is too heavy.

[hikalkan]

Which interfaces? Which consts? Can you be more specific?

[hikalkan]

If you mean IRepository, IDomainService... for example, it is impossible to move there. Domain.Shared project's responsibility is not that. These interfaces can not be shared with clients (remember domain.shared package's purpose).

[gdlcf88]

Hi all. I think this package can be made for the ETO abstractions.

I was trying to revise UserEto and wanted it to support the new entity synchronizer feature (since ABP v7.1). However, the IEntityEto<Key> interface is in the Volo.Abp.Ddd.Domain package, which contains a lot of infrastructure that doesn't belong to the shared layer (such as the DomainService class).

If we have a new shared package like @maliming mentioned, domain-shared layer projects can no longer depend on Volo.Abp.Ddd.Domain.

[hikalkan]

Good point. ETO classes and interfaces can go to that new package. So, @maliming go ahead. Domain package should depend on Domain.Shared. In this way, it won't be a breaking change. Also, please add this new package to Domain.Shared project in layered templates.