fix(api): expect absent rejectionReason instead of null - #41
Merged
Conversation
Video-service uses Jackson non_null serialization, which omits null fields entirely. The test expected rejectionReason: null in the response, but the field is absent when null. This was masked in CI because the hardcoded YouTube URL already existed (409 path), so the assertion was never reached. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
Summary
non_nullserialization behaviordefault-property-inclusion: non_null, so null fields are omitted from JSON responses rather than serialized asnulltoMatchObject({ rejectionReason: null })totoBeUndefined()Test plan
🤖 Generated with Claude Code