Add serialized node type exports #2914
Merged
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
matthew-plusprogramming
requested review from
trueadm,
zurfyx,
fantactuka,
acywatson,
tylerjbainbridge and
thegreatercurve
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
facebook-github-bot
added
the
CLA Signed
|
Carried over from the old PR: The |
matthew-plusprogramming
changed the title
SerializedParagraphNode and SerializedLineBreakNode type exports
thegreatercurve
approved these changes
Aug 31, 2022
|
@matthew-plusprogramming The tests are failing because you need to rebase this on top of |
thegreatercurve
pushed a commit
that referenced
this pull request
Nov 25, 2022
* Add `SerializedParagraphNode` and `SerializedLineBreakNode` type exports * Add `SerializedListItemNode` and `SerializedListNode` type exports * Add `SerializedMarkNode` type export
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.
Sorry if the similar PR to #2894 is bad practice, I'm new to contributing to OSS. The reason for this new PR is I changed the merge source branch name to reflect the changes now being made compared to previous changes.