ModelForgeLocal only
JSON → IR → deterministic code

JSON to C# model generator

Target
01

Source

VALID JSON
Local processing. Your JSON stays in this browser.
370 B
02

Model

4 MODELS
6 fields
SourceTarget
TypeEvidence
id
email_address
email
created_at
datetime
profile
tags
projects
4 fields
SourceTarget
TypeEvidence
display_name
active
phone
address
2 fields
SourceTarget
TypeEvidence
city
country
2 fields
SourceTarget
TypeEvidence
name
active
4 diagnosticsThe property name was normalized for the target. "email_address" → "emailAddress"
  • infoThe property name was normalized for the target. "email_address" → "emailAddress"PROPERTY_NAME_NORMALIZED
  • infoThe property name was normalized for the target. "created_at" → "createdAt"PROPERTY_NAME_NORMALIZED
  • infoThe property name was normalized for the target. "display_name" → "displayName"PROPERTY_NAME_NORMALIZED
  • warningOnly null was observed, so a concrete type cannot be inferred. "phone"NULL_ONLY_UNKNOWN_TYPE
03

Output

Awaiting generationInspect the model, choose a target, then commit the route.
JSONIRCODE
Hover a field to inspect its route
COMPILER NOTES

C# models with visible JSON contracts

ModelForge maps JSON evidence through the Universal Model IR into C# classes or records. Property aliases preserve original JSON names while nullable reference types keep missing and null evidence visible.

Common questions

Why are JsonPropertyName attributes generated?

C# property naming conventions can differ from source JSON names, so explicit aliases preserve the wire contract.

Is this target compiler-verified?

Golden fixtures are active, but verified status remains off until the recorded .NET SDK fixture compiles in the release environment.