Close #800 - add type tags info on JSON schema, and fix special character name bug. #808
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cter name bug of JSON schema. When generating JSON schema, type tags info are newly added to proper type by user request. Also, there had been a bug that generating wrong named JSON schema `$id` when special character being used in target type name, or generic type being used like `IPointer<T>`. JSON shcmea does not allow special character type name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When generating JSON schema, type tags info are newly added to proper type by user request.
Also, there had been a bug that generating wrong named JSON schema
$idwhen special character being used in target type name, or generic type being used likeIPointer<T>. JSON shcmea does not allow special character type name.