feat(docs): add explanation for NotionRenderer #315
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bytrangle
changed the title
|
Hello @transitive-bullshit This PR is a doc update. What else can I do to speed this up? |
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.
Description
NotionRenderer is one of the most important modules exported by
react-notion-x. Aside from the required proprecordMap, it accepts many optional props which makes it quite confusing to use for newcomers.Information that I added:
NotionRendererfullPageprop meansfullPage:header,pageHeader,footer,pageFooter!Notion Test Page ID
cc368b47772a4a1aa36e1f52c507d20d