Keep Original Enum Names for Reuse in Custom Templates#1763
Merged
RicoSuter merged 1 commit intoMar 29, 2025
Conversation
Owner
|
Thanks for the PR. |
This was referenced Sep 15, 2025
This was referenced Oct 16, 2025
This was referenced Oct 24, 2025
This was referenced Nov 3, 2025
This was referenced Nov 13, 2025
Merged
This was referenced May 1, 2026
This was referenced May 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces a new feature to retain the original enum names in the schema, allowing them to be reused in custom templates.
Custom templates often require the original/unchanged enum names (for proper annotations or description as an example). This enhancement ensures greater flexibility and customization for developers using NJsonSchema with custom enum templates.