Corvus.Json.JsonSchema.TypeGeneratorTool
Legacy shim for the generatejsonschematypes CLI tool. This tool has been renamed to corvusjson (package: Corvus.Json.Cli). Install the new tool with: dotnet tool install Corvus.Json.Cli. This shim delegates all commands to the same implementation with a deprecation warning.
Install
No framework information available.
README
Corvus.Json.CodeGenerator (Legacy)
This package has been renamed. The CLI tool is now
corvusjson, available in theCorvus.Json.Clipackage. This package (Corvus.Json.CodeGenerator) provides the legacygeneratejsonschematypescommand as a shim that delegates to the same code generation engine.New projects should install
Corvus.Json.Cliinstead:dotnet tool install --global Corvus.Json.Cli
Legacy shim behaviour
When you run generatejsonschematypes, it delegates to the same underlying implementation as corvusjson. The key difference is the default engine:
| Tool | Package | Default engine |
|---|---|---|
corvusjson |
Corvus.Json.Cli |
V5 (Corvus.Text.Json) |
generatejsonschematypes |
Corvus.Json.CodeGenerator |
V4 (Corvus.Json.ExtendedTypes) |
To generate V5 types with the legacy command, pass --engine V5 explicitly.
Migration
Replace your tool installation:
# Old
dotnet tool install --global Corvus.Json.CodeGenerator
# New
dotnet tool install --global Corvus.Json.Cli
Update your commands — schema generation is now a subcommand:
# Old
generatejsonschematypes person.json --rootNamespace MyApp.Models --outputPath Generated/
# New
corvusjson jsonschema person.json --rootNamespace MyApp.Models --outputPath Generated/
Other subcommands (config, validateDocument, listNameHeuristics, jsonata, jmespath, jsonlogic) just need the tool name changed:
# Old
generatejsonschematypes config myconfig.json
generatejsonschematypes validateDocument schema.json data.json
# New
corvusjson config myconfig.json
corvusjson validateDocument schema.json data.json
Documentation
See the CLI Code Generation guide for the full reference.
License
Apache 2.0 — see LICENSE.
Changes from Previous Version
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.