Enum support and write only fields #48
Open
Conversation
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
serializing enums as included string list not as a reference warn with log message for all exceptions not only for I/O exceptions warn about unhandled classes
treating WRITE_ONLY JSON fields as AUTO added error messages for meaningful error diagnosis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
So far enums were not supported and were incorrectly included as $refs although no schema was generated. With this patch enums are serialized as included string lists and not as reference anymore. The corresponding JUnit test was updated.
Write only fields have been omitted. This is also fixed.
In addition I have fixed:
warning with log message for all exceptions not only for I/O exceptions
warning about unhandled classes