Skip to content
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

Move TenantEto to the Volo.Abp.MultiTenancy.Abstractions project #18105

Open
1 task done
gdlcf88 opened this issue Nov 10, 2023 · 0 comments · May be fixed by #18107
Open
1 task done

Move TenantEto to the Volo.Abp.MultiTenancy.Abstractions project #18105

gdlcf88 opened this issue Nov 10, 2023 · 0 comments · May be fixed by #18107

Comments

@gdlcf88
Copy link
Contributor

gdlcf88 commented Nov 10, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

As a result, when a module needs to subscribe to TenantEto, it no longer needs to depend on the TenantManagement module. The latter is likely to be replaced by the application developers.

Describe the solution you'd like

We should move the TenantEto from the Volo.Abp.TenantManagement.Domain.Shared project to the Volo.Abp.MultiTenancy.Abstractions project.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant