feat: 🤖 Introduced animated typewriter functionality, allowing developers to seamlessly integrate the chat view for chatbot implementations. #311
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR introduces an animated typewriter effect for chat responses, similar to the animation seen in ChatGPT. The typewriter effect is applied exclusively to responses from the other user, ensuring a natural flow of dialogue. This feature was added to enhance the user experience for a chatbot I was working on. To implement this, I utilized the
animated_text_kitpackage.There are no breaking changes or modifications to existing APIs—this functionality simply enhances the current behavior without altering any core logic.
[ x] The title of my PR starts with a [Conventional Commit] prefix (
fix:,feat:,docs:etc).[x ] I have followed the [Contributor Guide] when preparing my PR.
I have updated/added tests for ALL new/updated/fixed functionality.
[ x] I have updated/added relevant documentation in
docsand added dartdoc comments with///.[ x] I have updated/added relevant examples in
examplesordocs.Yes, this PR is a breaking change.
[ x] No, this PR is not a breaking change.