docs: add {arrowleft} and {arrowright} special characters #486
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
kentcdodds
approved these changes
Nov 10, 2020
|
@all-contributors please add @sarahdayan for docs |
|
I've put up a pull request to add @sarahdayan! 🎉 |
|
🎉 This PR is included in version 12.2.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
What:
Documenting the new
{arrowleft}and{arrowright}special characters introduced in #404.Why:
The feature was released in 12.2.0 but not documented. This PR fixes it.
How:
I added the new special characters to the README. Since they're not meta characters, I added them before the list of meta characters instead of at the end of the list, for proper grouping.
Checklist: