gatsby: bug(www): some plugin READMEs are not properly rendered
Description
Plugin description is not rendering the Readme file properly, instead only README.md is visible.
Steps to reproduce
Visit https://www.gatsbyjs.org/packages/gatsby-plugin-sass/
Expected result
Readme gatsby-plugin-sass
should be transformed the same way as for other plugins
Actual result
What happened.
Environment
Windows, checked in Chrome and Edge
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 25 (14 by maintainers)
My colleague added a commit to your PR removing the same entry from the other packages mentioned here 😃
I’m still seeing the invalid README pages on the described plugins so I don’t think this issue is resolved just yet. @viveksharmaui are you still interested in helping with this issue?
Now it looks like the issue is resolved. I looked through the PRs since I experienced the issue this morning, but I didn’t find anything that specifically dealt with this issue. Here is a screenshot form the GraphQL query I ran this morning, and another that I ran just a few minutes ago after bringing my local repo up to date with the Gatsby one:
I think it’s safe to say this issue is no longer an active issue. Perhaps a pull request that was approved today contained the fix for this issue in it.
Sure! I will try
@viveksharmaui You can give it a try and request PR for this issue. The team will review your PR and will get back to you with the required changes if needed. Thanks
@viveksharmaui sure go for it!!
Similar Issues: #16322 #13720 #11129
Other Plugins with the same issue:
https://www.gatsbyjs.org/packages/gatsby-plugin-i18n/
https://www.gatsbyjs.org/packages/gatsby-plugin-i18n-tags/
https://www.gatsbyjs.org/packages/gatsby-plugin-i18n-readnext/
https://www.gatsbyjs.org/packages/gatsby-plugin-sass-resources/?=gatsby-plugin-sass
https://www.gatsbyjs.org/packages/bowlingx-gatsby-plugin-sass/?=gatsby-plugin-sass
https://www.gatsbyjs.org/packages/gatsby-plugin-sass-resources/?=gatsby-plugin-sass
It seems that the issue still persists. @wardpeet can you check this? (reference: #16322)