This page is the quickest map for changing parser or materialization behavior.
Public decode calls start in ToonDecoder.
Typical path:
ToonNode or the target CLR typesrc/DevOp.Toon/ToonDecoder.cssrc/DevOp.Toon/Internal/Decode/Scanner.cssrc/DevOp.Toon/Internal/Decode/Parser.cssrc/DevOp.Toon/Internal/Decode/NativeDecoders.cssrc/DevOp.Toon/Internal/Decode/TypedDecoder.cssrc/DevOp.Toon/Internal/Decode/DirectMaterializer.cssrc/DevOp.Toon/Internal/Decode/NativeTypedMaterializer.cssrc/DevOp.Toon/Internal/Decode/NativePathExpansion.csScanner turns source text into ParsedLine records with:
If a bug looks like indentation handling, line depth, tabs, or blank-line behavior, start here.
TypedDecoder first tries DirectMaterializer. If that fails, it records a miss and falls back to:
NativeDecodersNativeTypedMaterializerThis means typed decode bugs can live in either:
ExpandPaths = Safe can convert eligible dotted keys into nested objects. This logic is applied selectively and only when root-level conditions allow it. If a bug involves dotted keys or unexpectedly nested output, inspect:
ToonDecoderNativePathExpansionManualTests/ToonDecoderTests.csManualTests/ToonRoundTripTests.csManualTests/JsonComplexRoundTripTests.cstests/DevOp.Toon.Tests/GeneratedTestsIf strictness, indentation, or syntax handling changes, regenerate and rerun generated tests.