Language Management: Move feature definitions to application.contracts #18945
Description
Resolves #2064
Set the PR as breaking change, because even the namespace did not change, we moved from one layer to an another one.
Checklist
- I fully tested it as developer / designer and created unit / integration tests
- I documented it (or no need to document or I will create a separate documentation issue)
- I worked with the design team to get their idea for UI/UX design (or no need to design for this PR)
- I've assigned reviewer, related labels and set a milestone for this PR
How to test it?
Create a microservice template without dynamic localization being enabled, then in the microservice template make the following changes in several places (you can search in the root microservice directory):
- <PackageReference Include="Volo.Abp.LanguageManagement.EntityFrameworkCore" Version="9.0.0" />
+ <ProjectReference Include="C:\Github\volo\abp\language-management\src\Volo.Abp.LanguageManagement.EntityFrameworkCore\Volo.Abp.LanguageManagement.EntityFrameworkCore.csproj" />
Don't run the apps before making this change. Then, you can build & start all applications.