This repository has been archived by the owner on Jul 30, 2024. It is now read-only.
Fix webmodels mandatory type field regression #133
Merged
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 does 2 things
case objects
final
as well as minor adjustments to loggingtype
as a mandatory field. Even though the Nakadi API hastype
as a mandatory field forProblem
, this doesn't reflect in all errors that Nakadi returns which means that errors such asNoEmptySlotsOrCursorReset
didn't serialize properly because we were expecting aProblem
with atype
field. A test was also added to verify this. An issue at Make NoEmptySlotsOrCursorReset extend GeneralError again #134 has been made to track this.