DataSourceAdapter-Pattern + SiteExportService schlanker + Page-Services Scoped
- IDataSourceAdapter mit 3 Implementierungen (HANA, SAP_GATEWAY, MANUAL_EXCEL) und DataSourceAdapterResolver ersetzen das if/else auf ConnectionKind. - SiteExportService von 338 auf 187 Zeilen reduziert: Pipeline Resolve -> Fetch -> Transform -> Excel -> Central -> SharePoint. - Page-Services auf Scoped (per Blazor-Circuit); Orchestrator bleibt Singleton fuer geteilten Export-Status.
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
namespace TrafagSalesExporter.Services.DataSources;
|
||||
|
||||
public interface IDataSourceAdapter
|
||||
{
|
||||
/// <summary>
|
||||
/// Der Wert aus <see cref="Models.SourceSystemConnectionKinds"/>, den dieser Adapter behandelt.
|
||||
/// </summary>
|
||||
string ConnectionKind { get; }
|
||||
|
||||
Task<DataSourceFetchResult> FetchAsync(DataSourceFetchContext context);
|
||||
}
|
||||
Reference in New Issue
Block a user