This repository was archived by the owner on Jul 28, 2025. It is now read-only.
refactor: Split Data-related classes out into ServiceLayer.Common #15
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.
Description
Added ServiceLayer.Common project, with root namespace of ServiceLayer.
Moved data-related classes into this project, within ServiceLayer.Data
(note that EF model classes are hence in ServiceLayer.Data.Models; this namespace choice was intentional, to denote to devs that these classes represent EF models rather than pure POCOs)
Context
Allows data related functionality to be referenced from both the ServiceLayer.MESH deployable, and also future use such as from ServiceLayer.API
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.