I recently started adding collapsible sections to the Markdown files in my repo to hide certain sections as per the GitHub docs: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections
Markdown sample from the GitHub docs link above:
<details>
<summary>Tips for collapsed sections</summary>
### You can add a header
You can add text within a collapsed section.
You can add an image or a code block, too.
```ruby
puts "Hello World"
```
This led to an issue where GitHub pages was not rendering the HTML properly. Everything in the Markdown file beyond the first details tag was rendered as the original Markdown in plain unformatted text. I was able to correct this and fix it based on this answer deep in another repo's issue: gettalong/kramdown#155 (comment)
At the same time GH Pages weren't rendering, I observed that pyspelling appeared to be evaluating all text beyond the first details tag in the Markdown file for spelling issues. While the fix above resolved the rendering issue for GitHub Pages, it has not resolved it for pyspelling.
I understand that "pyspelling.filters.markdown" converts Markdown to HTML, then passes the HTML content off to pyspelling. I suspect the "pyspelling.filters.markdown" filter is also not processing the Markdown content after the first details tag in a Markdown file.
Here is a specific example from my repo where PySpelling is not working properly: https://github.com/microsoft/WhatTheHack/blob/master/015-Serverless/Student/Challenge-01.md#setup-local-workstation
Any suggestions on how to resolve this issue?
I recently started adding collapsible sections to the Markdown files in my repo to hide certain sections as per the GitHub docs: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections
Markdown sample from the GitHub docs link above:
This led to an issue where GitHub pages was not rendering the HTML properly. Everything in the Markdown file beyond the first details tag was rendered as the original Markdown in plain unformatted text. I was able to correct this and fix it based on this answer deep in another repo's issue: gettalong/kramdown#155 (comment)
At the same time GH Pages weren't rendering, I observed that pyspelling appeared to be evaluating all text beyond the first details tag in the Markdown file for spelling issues. While the fix above resolved the rendering issue for GitHub Pages, it has not resolved it for pyspelling.
I understand that "pyspelling.filters.markdown" converts Markdown to HTML, then passes the HTML content off to pyspelling. I suspect the "pyspelling.filters.markdown" filter is also not processing the Markdown content after the first details tag in a Markdown file.
Here is a specific example from my repo where PySpelling is not working properly: https://github.com/microsoft/WhatTheHack/blob/master/015-Serverless/Student/Challenge-01.md#setup-local-workstation
Any suggestions on how to resolve this issue?