-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(content-blog): add full blog post html into RSS/Atom feeds #4330
Conversation
[V1] Deploy preview failure Built without sensitive environment variables with commit 6d9942f https://app.netlify.com/sites/docusaurus-1/deploys/6044ac409059a4000850d678 |
Size Change: -46 B (0%) Total Size: 532 kB
ℹ️ View Unchanged
|
✔️ [V2] 🔨 Explore the source changes: c4d84b1 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61601d90517c5c000882b8d3 😎 Browse the preview: https://deploy-preview-4330--docusaurus-2.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR, this has been requested here already: #3719
Your implementation is not correct because it assume the blog post content is a simple string, which is not the case in practice as we use MDX
Read my comment here. on how you could transform an MDX string to an HTML string:
packages/docusaurus-plugin-content-blog/src/__tests__/__fixtures__/website/blog/long-text-r.md
Outdated
Show resolved
Hide resolved
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4330--docusaurus-2.netlify.app/ |
f465d4b
to
2c40c8b
Compare
Hi @slorber , Thanks for your review and reply. First commit is just backup to ensure the full blog rss content is expected behaviour I update content generate logic to make sure rss reader can get a readable, plain html string. So i remove import statement with And update testcase to ensure bigger cover range. |
3297c3a
to
a7c4054
Compare
Is any other problem for this pr? |
I'm not sure I understand why we need Regarding the PR, I'm pretty sure CC: @slorber |
because rss content should be a plain html, and in most custom component, its have their own javascript logic. Its will not a nice work in feed reader. Its just my mind |
Hi @MatanBobi , thanks for your review, i am move those into And for |
# Conflicts: # packages/docusaurus-plugin-content-blog/src/__tests__/__snapshots__/generateBlogFeed.test.ts.snap # packages/docusaurus-plugin-content-blog/src/__tests__/index.test.ts # packages/docusaurus-plugin-content-blog/src/blogUtils.ts # packages/docusaurus-utils/package.json # yarn.lock
Hey. After more tests, I'm finally merging this PR, as I think it is better than before and good enough for now. Keep in mind that the RSS feed content has some limitations that I documented here: #5664 |
Nice! Thanks for your code and time! RSS feature is soooo awesome for a RSS reader! |
Note, if you use In #5753 I temporarily swallow such errors, so if you have a blog post that doesn't render fully in the feed, it means there's an issue and we couldn't render it. See also #5664 for explainations |
Motivation
RSS Reader should get full content
Have you read the Contributing Guidelines on pull requests?
YEP
Test Plan
Just take a look of website rss xml file. and check item content
Further Plan
If accept this pr, i know my way is right and i will try to translate origin mdx to html, for make rss user have better experiences.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)