feat: support strikethrough mark #61
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
ben-basten
force-pushed
the
feat/missing-renderers
branch
from
c19bcbb to
6be2075
Compare
ben-basten
force-pushed
the
feat/missing-renderers
branch
from
6be2075 to
5379b54
Compare
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.
Add support for the strikethrough mark. Currently, if a strikethrough is used in Contentful it will break the render. This is a similar change to #53.
Strikethrough support was added in
@contentful/[email protected]: https://github.com/contentful/rich-text/releases/tag/%40contentful%2Frich-text-types%4016.5.0This should also resolve #58, by bumping the peer dependency.