Skip to content

Conversation

@krrishdholakia
Copy link
Contributor

@krrishdholakia krrishdholakia commented Nov 23, 2025

Title

feat(proxy_server.py): preserve content field even if null

Screenshot 2025-11-22 at 6 29 43 PM

Relevant issues

Addresses #16966

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

@vercel
Copy link

vercel bot commented Nov 23, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
litellm Ready Ready Preview Comment Nov 23, 2025 3:18am

@Praveena-617
Copy link

@krrishdholakia - Can we also ensure these fields ["role", "content", "tool_calls", "annotations", "function_call"]

@krrishdholakia
Copy link
Contributor Author

krrishdholakia commented Nov 23, 2025

@Praveena-617 tool calls and function call are not always set by the api (that's what led to the n8n error, where we were setting it to none, when it was expecting it to not exist)

i propose we start with content as being true always, and expand as we discover more edge cases

@krrishdholakia krrishdholakia merged commit 760bce2 into main Nov 24, 2025
49 of 59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants