NuGet ยท nuget

Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles

Core ConfigFile-Types for Eltheon Framework

Install

Install-Kommandos

dotnet add package Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles --version 0.9.2
<PackageReference Include="Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles" Version="0.9.2" />
paket add Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles --version 0.9.2
Install-Package Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles -Version 0.9.2

README

Vorschau

Redeon.SuperSiteEngineCore.Web.Eltheon.Core.ConfigFiles

Overview

This package manages hierarchical configuration for Eltheon. It contains base config file abstractions, serializers, discovery helpers, and the extension methods used by GlobalConfig to load strongly typed configuration objects from disk.

Capabilities

  • BaseConfigFile<T> handles JSON persistence (with polymorphic support) and path management using GlobalConfig.
  • ConfigsFile keeps a list of discovered IConfig implementations. GlobalConfig.Configs() bootstraps this file and scans all loaded assemblies for classes implementing IConfig.
  • Extension methods like GlobalConfig.GetConfig<T>() allow any feature to fetch its config payload without knowing the storage layout.
  • AddConfigsStore() registers ConfigFiles-owned canonical event metadata for safe configuration and template-owned database configuration signals.

Usage

  1. Ensure GlobalConfig.Initialize(path) has been invoked so config directories exist.
  2. Create a class implementing IConfig and place it in any loaded assembly.
  3. Call GlobalConfig.Instance.Configs().Load() (or the provided extensions) to populate the config list, then query it via GetConfig<T>().

Notes

  • The package uses Newtonsoft.Json with TypeNameHandling.Auto to persist polymorphic trigger/config types. Do not remove type metadata unless you control all config consumers.
  • Because the extension scans every loaded assembly, keep config classes lightweight to avoid large static initialization costs at startup.
  • Configuration/data events never include raw values, secrets, or connection strings. Payloads carry config names, changed keys, provider/context names, redaction flags, and generic reason codes only.