Introduce JSON type and use it for OCPP and internal message structure

[e-mobility-charging-stations-simulator.git] / src / types / ocpp / 1.6 / ChargingProfile.ts

diff --git a/src/types/ocpp/1.6/ChargingProfile.ts b/src/types/ocpp/1.6/ChargingProfile.ts
index e4a66d786eb4a82fefd82b460832db616f3ac276..6416bf5d1bd2f0e25a10c58e79641cb4e891c874 100644 (file)
--- a/src/types/ocpp/1.6/ChargingProfile.ts
+++ b/src/types/ocpp/1.6/ChargingProfile.ts
@@ -1,5 +1,6 @@
+import { JsonType } from '../../JsonType';
 
-export interface ChargingProfile {
+export interface OCPP16ChargingProfile extends JsonType {
   chargingProfileId: number;
   transactionId?: number;
   stackLevel: number;
@@ -11,7 +12,7 @@ export interface ChargingProfile {
   chargingSchedule: ChargingSchedule;
 }
 
-export interface ChargingSchedule {
+export interface ChargingSchedule extends JsonType {
   duration?: number;
   startSchedule?: Date;
   chargingRateUnit: ChargingRateUnitType;
@@ -19,7 +20,7 @@ export interface ChargingSchedule {
   minChargeRate?: number;
 }
 
-export interface ChargingSchedulePeriod {
+export interface ChargingSchedulePeriod extends JsonType {
   startPeriod: number;
   limit: number;
   numberPhases?: number;