chat-ui-react: update chat-headless-react dependency #92
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates chat-ui-react to use chat-headless-react v0.9.5, allowing us to use the latest version of yext/analytics
vijay267
reviewed
Mar 14, 2025
| * */ | ||
| const testEnvironment = 'DEV'; | ||
| // eslint-disable-next-line @typescript-eslint/ban-ts-comment | ||
| // @ts-ignore |
There was a problem hiding this comment.
Does it make sense to refactor it so that the urls are shared? If I'm not mistaken, the 2 URLs are the same outside of the /streaming on the 2nd one right?
anguyen-yext2
approved these changes
Mar 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates chat-ui-react to use chat-headless-react v0.9.5, allowing us to use the latest version of yext/analytics
J=WAT-4671
TEST=auto, manual
Unit and integration tests pass.
Spun up test-site locally with sandbox model. Was able to make requests and receive responses as expected, confirmed analytics events were going through for responses, impressions, and link clicks.