Repository navigation
fix: drop misleading extensions json tag on ProblemDetails - #25
Conversation
MarshalJSON/UnmarshalJSON flatten extension members to the top level, so the nested "extensions" tag was never used. Closes #19 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FHBdej3KvFACHzafbEhw7C
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 58 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #25 +/- ##
=======================================
Coverage 86.27% 86.27%
=======================================
Files 14 14
Lines 583 583
=======================================
Hits 503 503
Misses 62 62
Partials 18 18 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Closes #19
ProblemDetails.Extensionstagjson:"extensions,omitempty"→json:"-", with a comment explaining thatMarshalJSON/UnmarshalJSONflatten members to the top level.extensionskey is emitted.No wire-format change.
Generated by Claude Code