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.