Normalize message and handle empty input in MessageParser component in chatbot #635
Conversation
This file contains 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
…n chatbot [[Bug] Chatbot Message Sent Without Text Priyaaa1#555]
✅ Deploy Preview for startconnect-hub ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@RealNickey the issue is not assigned to you, you will not get any points on merging this PR. |
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.
This pull request fixes the issue where a message is sent directly to the chatbot without any text being entered by the user. The
MessageParsercomponent in the chatbot has been updated to normalize the message by converting it to lowercase and removing leading/trailing spaces. Additionally, the component now handles empty input by displaying a default response and stopping further processing. This ensures that an empty message is not sent to the chatbot.Fixes #555