directory-to-object
0.3.1
dotnet add package directory-to-object --version 0.3.1
NuGet\Install-Package directory-to-object -Version 0.3.1
<PackageReference Include="directory-to-object" Version="0.3.1" />
<PackageVersion Include="directory-to-object" Version="0.3.1" />
<PackageReference Include="directory-to-object" />
paket add directory-to-object --version 0.3.1
#r "nuget: directory-to-object, 0.3.1"
#:package directory-to-object@0.3.1
#addin nuget:?package=directory-to-object&version=0.3.1
#tool nuget:?package=directory-to-object&version=0.3.1
directory-to-object-dotnet
.NET implementation of the directory-to-object configuration reader library, tailored to the System.Text.Json JSON parser.
As with its TypeScript ancestor, this library is for complicated configuration cases where having just one structured file is too limiting or is hard for humans to understand. Instead of cramming all the configuration into one structured file, this library will combine configuration data split across multiple files in a directory into a single System.Text.Json.Nodes JsonObject. Consuming code sees the directory contents as the equivalent of a single configuration file.
The library targets .NET 10 (net10.0), .NET 8.0 (net8.0) and netstandard2.0 for maximum compatibility.
Using the library
Install from NuGet
dotnet add package directory-to-object
Build locally
Simply:
dotnet build
To run the TUnit tests from the command line (substitute a different framework identifier, as needed):
dotnet run --project directory-to-object.Tests/directory-to-object.Tests.csproj --framework=net10.0
Reference documentation
Documentation for the latest version of the library is available at: directory-to-object-dotnet.scroogieboy.com.
Examples
Simple loading
The simplest example is to use the default settings for the loader (which treats files with the ".json" extension as JSON and files with the ".txt" extension as plain text files):
using DirectoryToObject;
// Get a directory loader with default options.
var loader = Loader.Default;
// Load a directory from the file system, specified by path, into a JsonObject.
var contents = await loader.LoadFileSystemPathIntoJsonObjectAsync("path/to/my/directory");
Directories as arrays
It's sometimes useful to represent arrays of objects as directories of JSON files. The library now supports loading directories directly as arrays (using the LoadDirectoryIntoJsonArrayAsync extension method) or by specifying explicit loading instructions. For example (from the tests):
var loader = Loader.FromHandlerCollection(
[
Handler.JsonFile.WhenExtensionIsOneOf(".json"),
Handler.TextFile.WhenExtensionIsOneOf(".txt"),
Handler.Directory.WhenPathMatchesAny("spec/containers", "spec/volumes").AsArray("name")
]);
var manifest = await loader.LoadFileSystemPathIntoJsonObjectAsync(manifestDirectoryPath);
This snippet informs the loader to treat the directories at the "spec/containers" and "spec/volumes" relative paths as arrays, mapping the file name into the "name" property of every loaded object.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen40 was computed. tizen60 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Microsoft.Extensions.FileSystemGlobbing (>= 10.0.9)
- System.Text.Json (>= 10.0.7)
-
net10.0
- Microsoft.Extensions.FileSystemGlobbing (>= 10.0.9)
-
net8.0
- Microsoft.Extensions.FileSystemGlobbing (>= 10.0.9)
- System.Text.Json (>= 10.0.7)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on directory-to-object:
| Package | Downloads |
|---|---|
|
toml-to-object
Extension for the directory-to-object package to support loading of TOML files in directories. |
GitHub repositories
This package is not used by any popular GitHub repositories.