Fix typing indicator - Round #2 #136
Open
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
* Add typing indicator * Update readme to include typing feature * fix sample code issue in readme * Update demo to include typing example * Remove vendor prefixes from typing indicator style * Update typing indicator prop name * Add missing comma
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.
Description
This is the second try to merge #127 - the first try had a bug so we reverted without having time to investigate.
@kaxi1993 Really did all the heavy lifting here! Sorry for the delay in getting it out!
Checklist
npm start) to ensure it still functions as expected, and/ornpm run lintpasses (npm run lint -- --fixwill autofix where possible)