You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visit https://www.gatsbyjs.org/blog/ (or scroll to the bottom of https://www.gatsbyjs.org under Latest from the Gatsby blog) and look at excerpt for Delivering Modern Website Experiences: The Journey to a Content Mesh from October 4 (currently the second result).
Actual result
The CMS was born to make content sites possible . Now, it’s being reimagined to make them incredible . In the early 2000s, publishing on…
Note the extra space after "possible" and "incredible", before each period. Inspecting the DOM, I see extra spaces on both sides of those words:
The CMS was born to make content sites possible .
Now, it’s being reimagined to make them incredible .
In the early 2000s, publishing on…
Looking at the Markdown source, it looks like underscores are getting replaced by spaces while generating the excerpt.
Expected result
This depends on whether the excerpt is intended to be plaintext or formatted.
If plaintext, I would expect the underscores to get stripped out entirely, leaving no space before each period.
If formatted, I would expect the words possible and incredible to be italicized.
Comments
I assume this bug (if it is a bug) lies in gatsby-transformer-remark but I'm hoping that someone more familiar with the codebase will be able to clarify the expected behavior and where that behavior is implemented. I wouldn't mind picking this up for Hacktoberfest… 👻
The text was updated successfully, but these errors were encountered:
I think it should be formatted - there is open issue for it #4459 and PR for it #5586 - PR is abandoned now, so you can use that as starting point. I'll go to PR to document what need to be done there
Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!
It’s been 30 since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
Thanks again for being part of the Gatsby community!
Steps to reproduce
Visit https://www.gatsbyjs.org/blog/ (or scroll to the bottom of https://www.gatsbyjs.org under Latest from the Gatsby blog) and look at excerpt for Delivering Modern Website Experiences: The Journey to a Content Mesh from October 4 (currently the second result).
Actual result
Note the extra space after "possible" and "incredible", before each period. Inspecting the DOM, I see extra spaces on both sides of those words:
Looking at the Markdown source, it looks like underscores are getting replaced by spaces while generating the excerpt.
Expected result
This depends on whether the excerpt is intended to be plaintext or formatted.
If plaintext, I would expect the underscores to get stripped out entirely, leaving no space before each period.
If formatted, I would expect the words possible and incredible to be italicized.
Comments
I assume this bug (if it is a bug) lies in gatsby-transformer-remark but I'm hoping that someone more familiar with the codebase will be able to clarify the expected behavior and where that behavior is implemented. I wouldn't mind picking this up for Hacktoberfest… 👻
The text was updated successfully, but these errors were encountered: