Added the ability to define an explicit type with $corvusTypeName
.
#366
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you add a
$corvusTypeName
keyword to a schema and give it astring
value, it will be used as the basis for the type name of the schema, overriding the default naming convention.If the value is present, and is a string of
Length >= 1
, it will converted into a PascalCased basis for the type name.Naming collisions will still be resolved in the usual way.
For example:
File:
test.json