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.

Sign up for GitHub

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

Jump to bottom

Remove the Tenant Info Requirement from Repositories #41

Open
tsutomi opened this issue Oct 16, 2024 · 0 comments
Open

Remove the Tenant Info Requirement from Repositories #41

tsutomi opened this issue Oct 16, 2024 · 0 comments
Assignees
@tsutomi
Labels
enhancement New feature or request

Comments

@tsutomi
Copy link
Member

tsutomi commented Oct 16, 2024

Problem Context
The current EntityFramework-based implementation of the repository overloads the cases in which the tenant should segregate the data.

This approach was done to allow the manual creation of instances of the repository in background applications, which were not manually operated by a user.

Proposed Solution
We should remove the direct dependency from Finbuckle MultiTenant project from the repositories, allowing the per-tenant segregation to happen in the application configuration, and letting the repositories to trust the source data correct segregation.
@tsutomi tsutomi added the enhancement New feature or request label Oct 16, 2024
@tsutomi tsutomi self-assigned this Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsutomi tsutomi

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

41-remove-the-tenant-info deveel/deveel.repository
1 participant
@tsutomi