-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Nullable types #20
Comments
Thinking of looking into this for Hacktoberfest. Any pointers? |
We generate a Document which contains Messages, each message has a Payload. This When we set the An example of a simple schema representing a non-nullable int: {
"type": "integer"
} An example representing a nullable int: {
"type": ["integer", "null"]
} We need to make We can optionally/additionally support the OpenAPI spec which defines an additional property
|
This is implemented using a Same as NJsonSchema I suppose this is the easiest way to be able to set this as one or more value. // for non-nullable primitives
Type = JsonSchemaType.Integer;
// for nullable-primitives
Type = JsonSchemaType.Integer | JsonSchemaType.Null; This also allows for setting the nullable type separate from the underlying type;
|
Closing in favor of #60 |
See #16
The text was updated successfully, but these errors were encountered: