mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 17:56:02 +03:00
[GH-ISSUE #541] MSBuild-integrated Markdown linting for .NET projects #444
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#444
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 @Piedone on GitHub (Jul 29, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/541
(I'd have opened a Discussions thread for this if that feature would be enabled. Sorry if this is not a good place for such show and tell announcements.)
Something curious you might like: In our Lombiq Node.js Extensions project we've added Markdown linting, utilizing markdownlint too, in a way that it automatically runs as part of an MSBuild build process. This means that for .NET projects, lining for Markdown files happens automatically, as part of the normal build, and you get linter errors as build errors. This is how .NET static code analysis works as well, so this way, Markdown linting fits seamlessly into the .NET developer experience. See docs here.
What do you think?
@DavidAnson commented on GitHub (Jul 29, 2022):
This sounds awesome! If you want to send a PR to add a link to the "Related "section of the README, that may help spread the word. (Please have a look at CONTRIBUTING.md before doing so.)
@Piedone commented on GitHub (Jul 29, 2022):
Great idea, thanks, will do that.