dotnet/eShop

Share model classes between projects

Open

#18 创建于 2023年11月1日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)C# (10,453 star) (3,622 fork)batch import
good first issuehelp wanted

描述

From @ReubenBond:

Currently, each project which needs a representation of an Order has its own representation. This makes refactoring complex and it leads to inconsistencies. Instead, we should have one or more shared projects which define the domain model.

If we see a benefit to having a mapped type in some cases (eg, types used in Blazor view models), we should do so, but we should simplify where we can.

贡献者指南

技术栈
csharp
领域
backend
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C#.NETeShop codebase
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate the current representation of Order in each project. Identify duplicated model classes across projects like Ordering.API and Ordering.Domain. Plan to move shared models into a common project, e.g., Ordering.Shared. Consider using partial classes or inheritance for any view model specific mappings.
Share model classes between projects · dotnet/eShop#18 | Good First Issue