Create global PlatformPlatform solution and extract reusable backend foundation #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l the Domain and Application classes from Foundation
…idation, Identity, Cqrs, and DomainEvents
…or to new Behaviors namespace
…epositories like TenantRepository
…he root folder and remove src and tests folders
…egistrations fluent registration
…ects being tested
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
This pull request establishes a new top-level PlatformPlatform .NET solution, replacing the former AccountManagement solution. It extracts a reusable backend-foundation from account management. The previous Foundation project is divided into three sub-projects:
DomainModeling,InfrastructureCore, andAspNetCoreUtils. This division ensures that dependencies don't leak into other areas.These projects introduce a meaningful namespace structure that includes
Entities,Persistence,Validation,Identity,Cqrs,DomainEvents, etc.Several minor refactorings have been performed to enhance the overall clarity of the solution. For example, the creation of a
RepositoryBase<T, TId>removes the boiler code needed to create a concrete repository like TenantRepository. Furthermore, service registration now utilizes a fluent API for greater readability and efficiency.Checklist