-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add support for custom resolution of whether a message is ai generated #2572
Conversation
Size Change: +268 B (+0.02%) Total Size: 1.17 MB
ℹ️ View Unchanged
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2572 +/- ##
==========================================
- Coverage 82.97% 82.95% -0.02%
==========================================
Files 444 444
Lines 9221 9222 +1
Branches 2254 2254
==========================================
- Hits 7651 7650 -1
- Misses 1237 1239 +2
Partials 333 333 ☔ View full report in Codecov by Sentry. |
## [12.7.1](v12.7.0...v12.7.1) (2024-12-05) ### Bug Fixes * add support for custom resolution of whether a message is ai generated ([#2572](#2572)) ([54640ac](54640ac))
🎉 This PR is included in version 12.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Submit a pull request
🎯 Goal
With the introduction of the AI feature in the SDK, we introduced a behaviour that checks for
message.ai_generated
and manages the UI based on that. This is very wrong, as this field (potentially) comes as a custom property and its place is not in the SDK. Instead, we introduce a new property calledisMessageAIGenerated
, which is a factory function that controls the custom behaviour of figuring out whether a message is AI generated or not (which would vary from integration to integration). It also makes sure this isn't a breaking change for the SDK any longer.🛠 Implementation details
Provide a description of the implementation
🎨 UI Changes
Add relevant screenshots