Update Markdown & Reimplement Syntax Highlighting #19
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
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 PR attempts to mitigate the errors from issue #18. While this doesn't fix the error itself, it does allow us to replace small pieces of content in the article to prevent the error.
The error itself only occurs with
react-syntax-highlighterwhen parsing code blocks. It seems to only happen when there are characters such as@along with numbers and decimals. For example, this error occurs with the following code block:```bash
ssh [email protected]
```
This PR forces
react-syntax-highlighterto activate only when a language is set. So to fix the above, we remove the Bash language from the syntax highlighting from below.```
ssh [email protected]
```
Unfortunately, I haven't had any success with fixing the error itself and both libraries are on the latest versions. I've tried reimplementing the syntax highlighter code multiple times to see if it resolves the issue, but sadly no luck.