feat(core): Add enableTruncation option to OpenAI integration#20167
feat(core): Add enableTruncation option to OpenAI integration#20167andreiborza wants to merge 3 commits intodevelopfrom
enableTruncation option to OpenAI integration#20167Conversation
This PR adds an `enableTruncation` option to the OpenAI integration that allows users to disable inpute message truncation. It defaults to `true` to preserve existing behavior. Closes: #20135
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Core
Deps
Other
Bug Fixes 🐛Core
Other
Internal Changes 🔧Core
Deps
Other
🤖 This preview updates automatically when you update the PR. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 03ad550. Configure here.
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
| }), | ||
| ], | ||
| beforeSendTransaction: event => { | ||
| if (event.transaction.includes('/openai/')) { |
There was a problem hiding this comment.
This drops the express http transaction afaik, so that we can use the testing framework's .expect({ transaction } and match the ai transaction instead.
The other scenarios also do this.

This PR adds an
enableTruncationoption to the OpenAI integration that allows users to disable input message truncation. It defaults totrueto preserve existing behavior.Closes: #20135