From 9de94bd65ff5733464cc190f047087198af14cbd Mon Sep 17 00:00:00 2001 From: Neil Dorin Date: Mon, 22 Sep 2025 15:05:06 -0600 Subject: [PATCH] fix: Update v2 config detection criteria Changed the logic for identifying v2 configuration files. The check now looks for the presence of a "versions" node instead of the absence of "system" or "template" nodes, reflecting an update in the configuration file structure. --- .../Config/Essentials/ConfigReader.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PepperDash.Essentials.Core/Config/Essentials/ConfigReader.cs b/src/PepperDash.Essentials.Core/Config/Essentials/ConfigReader.cs index ea5d2672..2591e8aa 100644 --- a/src/PepperDash.Essentials.Core/Config/Essentials/ConfigReader.cs +++ b/src/PepperDash.Essentials.Core/Config/Essentials/ConfigReader.cs @@ -129,10 +129,10 @@ namespace PepperDash.Essentials.Core.Config { var parsedConfig = JObject.Parse(fs.ReadToEnd()); - // Check if it's a v2 config (missing "system" or "template" nodes) + // Check if it's a v2 config (check for "version" node) // this means it's already merged by the Portal API // from the v2 config tool - var isV2Config = parsedConfig["system"] == null || parsedConfig["template"] == null; + var isV2Config = parsedConfig["versions"] != null; if (isV2Config) {