37 lines
1.9 KiB
Markdown
37 lines
1.9 KiB
Markdown
|
---
|
||
|
|
source_files:
|
||
|
|
- Common/DTS.Common/Interface/EngineerDetails/IEngineerDetailsView.cs
|
||
|
|
- Common/DTS.Common/Interface/EngineerDetails/IEngineerDetailsViewModel.cs
|
||
|
|
generated_at: "2026-04-17T16:24:45.886852+00:00"
|
||
|
|
model: "zai-org/GLM-5-FP8"
|
||
|
|
schema_version: 1
|
||
|
|
sha256: "f5d1f678485734fd"
|
||
|
|
---
|
||
|
|
|
||
|
|
# EngineerDetails
|
||
|
|
|
||
|
|
### Purpose
|
||
|
|
This module defines the view and view model contracts for the Engineer Details feature within the DTS application. It follows the MVVM (Model-View-ViewModel) architectural pattern, providing empty marker interfaces that extend base view/view model types to enable dependency injection and view binding for engineer-related UI components.
|
||
|
|
|
||
|
|
### Public Interface
|
||
|
|
|
||
|
|
**IEngineerDetailsView** (`IEngineerDetailsView.cs`)
|
||
|
|
- Signature: `public interface IEngineerDetailsView : IBaseView`
|
||
|
|
- Description: Marker interface for the Engineer Details view. Inherits from `IBaseView` but defines no additional members.
|
||
|
|
|
||
|
|
**IEngineerDetailsViewModel** (`IEngineerDetailsViewModel.cs`)
|
||
|
|
- Signature: `public interface IEngineerDetailsViewModel : IBaseViewModel`
|
||
|
|
- Description: Marker interface for the Engineer Details view model. Inherits from `IBaseViewModel` but defines no additional members.
|
||
|
|
|
||
|
|
### Invariants
|
||
|
|
- Both interfaces must inherit from their respective base types (`IBaseView`, `IBaseViewModel`) to maintain consistency with the application's MVVM framework.
|
||
|
|
- All implementations must reside in the `DTS.Common.Interface` namespace.
|
||
|
|
|
||
|
|
### Dependencies
|
||
|
|
- **Depends on**: `DTS.Common.Base` (for `IBaseView` and `IBaseViewModel` base interfaces)
|
||
|
|
- **Depended on by**: Unknown from source alone (likely concrete view/view model implementations and DI container registration)
|
||
|
|
|
||
|
|
### Gotchas
|
||
|
|
- Both interfaces are empty marker interfaces. Any behavior contracts must be defined in extending interfaces or concrete implementations. The purpose of these empty interfaces is unclear from source alone—they may exist for DI registration, type discrimination, or future extensibility.
|
||
|
|
|
||
|
|
---
|