dotnet/eShop

Share model classes between projects

Open

Aperta il 1 nov 2023

Vedi su GitHub
 (3 commenti) (0 reazioni) (1 assegnatario)C# (10.453 star) (3622 fork)batch import
good first issuehelp wanted

Descrizione

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.

Guida contributor

Tech stack
csharp
Dominio
backend
Tipo issue
refactor
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
C#.NETeShop codebase
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
35
Direzione di ricerca
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.