-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Feat/sources in react widget #1317
base: main
Are you sure you want to change the base?
Feat/sources in react widget #1317
Conversation
… widget, handled sources data.type, and rendering sources when available
…into feat/sources-in-react-widget
@utin-francis-peter is attempting to deploy a commit to the Arc53 Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…l to make theme props available globally
…into feat/sources-in-react-widget
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1317 +/- ##
=======================================
Coverage 34.02% 34.02%
=======================================
Files 69 69
Lines 3377 3377
=======================================
Hits 1149 1149
Misses 2228 2228 ☔ View full report in Codecov by Sentry. |
…into feat/sources-in-react-widget
…into feat/sources-in-react-widget
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature in review.
Why was this change needed? (You can also link to an open issue here)
This update will make it possible for users to view the source of generated responses to their queries when interacting with the widget.
Other information:
After series of implementations through trials and research, the sources still refuses to render as expected. Please I'll appreciate some reviews of current implementation and helpful discussions around it. Thank you.
Also, there seems to be a bug I didn't account for in this PR, but pre the actual generated response, an "undefined" response is rendered into the bubble. On actual response rendering, the initial "undefined" text gets concatenated to the actual responses. I'm willing to make a PR after current issue is resolved.
closes: #1289