refactor: Naming-Konventionen für digitaleEingaenge umgesetzt
- digitaleEingaengeMockData.js = strukturierte Datenbasis für Development - digitaleEingaengeAPIHandler.ts = API-Endpunkt zur Auslieferung im Dev - fetchDigitaleEingaengeService.ts = Service zur Umwandlung von window-Variablen - Naming-Schema sorgt für klare Struktur und gute Lernbarkeit
This commit is contained in:
20
services/fetchSingleTDMDataService.ts
Normal file
20
services/fetchSingleTDMDataService.ts
Normal file
@@ -0,0 +1,20 @@
|
||||
// /services/fetchSingleTDMDataService.ts
|
||||
|
||||
export const fetchTDMDataBySlot = async (slot: number): Promise<any> => {
|
||||
if (typeof window === "undefined") return null;
|
||||
|
||||
const isDev = process.env.NEXT_PUBLIC_NODE_ENV === "development";
|
||||
|
||||
const url = isDev
|
||||
? `/apiMockData/TDM/slot${slot}.json`
|
||||
: `${window.location.origin}/CPL?Service/empty.acp&TDM=${slot}`;
|
||||
|
||||
try {
|
||||
const res = await fetch(url);
|
||||
if (!res.ok) throw new Error(`HTTP ${res.status}`);
|
||||
return await res.json();
|
||||
} catch (error) {
|
||||
console.error(`❌ Fehler beim Laden von Slot ${slot}:`, error);
|
||||
return null;
|
||||
}
|
||||
};
|
||||
Reference in New Issue
Block a user