Fixes errors caused by special characters #17
Merged
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
jfreda
approved these changes
Feb 27, 2023
anuragprafulla
referenced
this pull request
in razorpay/hermes
Jun 27, 2023
* Add `cleanString` function * Update yarn.lock
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.
Applies a
cleanStringfunction to editable Document properties to replace invalid characters with ASCII-friendly equivalents. This fixes an error where creating or saving a doc with special characters, e.g., smart quotes, bullets, accented letters, would throw an error and sometimes delete the document header.I consider this a short-term solution while we investigate how to make special characters work.
New dependency: https://www.npmjs.com/package/replace-special-characters