mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #65] support for frontmatter in the middle of the text #1900
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#1900
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @igalic on GitHub (Jul 21, 2017).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/65
Some of our markdown documents have frontmatter, but also… "middle-matter"
that frontmatter uses the exact same style, and usually declares (sub) sections:
is there any way we can rig the frontmatter config to — optionally — support that, too?
@igalic commented on GitHub (Jul 21, 2017):
i've committed a fix to one of our blogs, referencing this so you can see what it looks like!
@DavidAnson commented on GitHub (Jul 21, 2017):
Is middle-matter a real thing, or something custom with your process? I have an idea and may implement this regardless, but would feel better about the investment if I knew it was a widespread need. :)
@igalic commented on GitHub (Jul 22, 2017):
the "engine" we use is metalsmith
and now i'm trying to remember where else i've seen this
@DavidAnson commented on GitHub (Oct 26, 2017):
I've done research on two occasions and can't find any documentation/specification that describes the use of front matter in the middle of a file as shown above.
While I could guess at how "middle matter" is expected to behave, it seems like it's rare in the wild AND you have a confirmed workaround in the form of
markdownlint-disable. Therefore, I'm closing this issue for now.If you find a specification and can point to significant use in practice, I'm happy to revisit this.
Thanks!
@edobry commented on GitHub (May 4, 2023):
I know this was closed years ago but I have a related usecase, namely ignoring a generated section at the end of the file. My document is a README for a Terraform module, which has some handwritten Markdown, and then a section which gets filled in by a tool called
terraform-docsin between these markers:The generated Markdown is not compliant with my rules and it would be difficult to make it be so, and not really important. Right now i'm able to make this work with the following format:
but it would be quite nice to be able to configure markdownlint to instead match on those existing markers.
@DavidAnson commented on GitHub (May 4, 2023):
See #249