Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/SimonCropp/MarkdownSnippets
Extracts snippets from code files and merges them into markdown documents.
https://github.com/SimonCropp/MarkdownSnippets
Last synced: about 2 months ago
JSON representation
Extracts snippets from code files and merges them into markdown documents.
- Host: GitHub
- URL: https://github.com/SimonCropp/MarkdownSnippets
- Owner: SimonCropp
- License: mit
- Created: 2019-02-07T21:18:54.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2024-05-01T09:54:16.000Z (5 months ago)
- Last Synced: 2024-05-01T12:34:23.757Z (5 months ago)
- Language: C#
- Homepage:
- Size: 2.47 MB
- Stars: 178
- Watchers: 6
- Forks: 24
- Open Issues: 5
-
Metadata Files:
- Readme: readme.md
- Funding: .github/FUNDING.yml
- License: license.txt
- Code of conduct: code_of_conduct.md
Awesome Lists containing this project
- jimsghstars - SimonCropp/MarkdownSnippets - Extracts snippets from code files and merges them into markdown documents. (C# #)
README
# 
MarkdownSnippets
[](https://ci.appveyor.com/project/SimonCropp/MarkdownSnippets)
[](https://www.nuget.org/packages/MarkdownSnippets.Tool/)
[](https://www.nuget.org/packages/MarkdownSnippets.MsBuild/)
[](https://www.nuget.org/packages/MarkdownSnippets/)
A [dotnet tool](https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools) that extract snippets from code files and merges them into markdown documents.
**See [Milestones](../../milestones?state=closed) for release notes.**
**[.net 8](https://dotnet.microsoft.com/download/dotnet/8.0) or higher is required to run this tool.**
## Value Proposition
Automatically extract snippets from code and injecting them into markdown documents has several benefits:
* Snippets can be verified by a compiler or parser.
* Tests can be run on snippets, or snippets can be pulled from existing tests.
* Changes in code are automatically reflected in documentation.
* Snippets are less likely to get out of sync with the main code-base.
* Snippets in markdown is easier to create and maintain since any preferred editor can be used to edit them.
## Behavior
* Recursively scan the target directory for code files containing snippets. (See [exclusion](/docs/exclusion.md)).
* Recursively scan the target directory for markdown (`.md` or `mdx`) files. (See [Document Scanning](#document-convention)).
* Merge the snippets into those markdown files.
## Installation
Ensure [dotnet CLI is installed](https://docs.microsoft.com/en-us/dotnet/core/tools/).
Install [MarkdownSnippets.Tool](https://nuget.org/packages/MarkdownSnippets.Tool/)
```ps
dotnet tool install -g MarkdownSnippets.Tool
```
## Usage
```ps
mdsnippets C:\Code\TargetDirectory
```
If no directory is passed the current directory will be used, but only if it exists with a git repository directory tree. If not an error is returned.
### Document Convention
There are two approaches scanning and modifying markdown files.
#### SourceTransform
This is the default.
##### source.md file
The file convention recursively scans the target directory for all `*.source.md` files. Once snippets are merged the `.source.md` to produce `.md` files. So for example `readme.source.md` would be merged with snippets to produce `readme.md`. Note that this process will overwrite any existing `.md` files that have matching `.source.md` files.
#### mdsource directory
There is a secondary convention that leverages the use of a directory named `mdsource`. Where `.source.md` files are placed in a `mdsource` sub-directory, the `mdsource` part of the file path will be removed when calculating the target path. This allows the `.source.md` to be grouped in a sub directory and avoid cluttering up the main documentation directory.
When using the `mdsource` convention, all references to other files, such as links and images, should specify the full path from the root of the repository. This will allow those links to work correctly in both the source and generated markdown files. Relative paths cannot work for both the source and the target file.
#### InPlaceOverwrite
Recursively scans the target directory for all `*.md` files and merges snippets into those files.
##### Command line
```ps
mdsnippets -c InPlaceOverwrite
```
```ps
mdsnippets --convention InPlaceOverwrite
```
##### Config file
Can be enabled in [mdsnippets.json config file](/docs/config-file.md).
```json
{
"Convention": "InPlaceOverwrite"
}
```
#### Moving from SourceTransform to InPlaceOverwrite
* Ensure `"WriteHeader": false` is used in `mdsnippets.json`.
* Ensure `"ReadOnly": false` is used in `mdsnippets.json`.
* Ensure using the current stable version and a docs generation has run.
* Delete all `.source.md` files.
* Modify `mdsnippets.json` to add `"Convention": "InPlaceOverwrite"`.
* Run the docs generation.
### Mark resulting files as read only
To mark the resulting documents files as read only use `-r` or `--read-only`.
This can be helpful in preventing incorrectly editing the documents file instead of the `.source.` file conventions.
```ps
mdsnippets -r true
```
```ps
mdsnippets --read-only true
```
## Defining Snippets
Any code wrapped in a convention based comment will be picked up. The comment needs to start with `begin-snippet:` which is followed by the key. The snippet is then terminated by `end-snippet`.
```
// begin-snippet: MySnippetName
My Snippet Code
// end-snippet
```
Named [C# regions](https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-region) will also be picked up, with the name of the region used as the key.
To stop regions collapsing in Visual Studio [disable 'enter outlining mode when files open'](/docs/stop-regions-collapsing.png). See [Visual Studio outlining](https://docs.microsoft.com/en-us/visualstudio/ide/outlining).
### UrlsAsSnippets
Urls to files to be included as snippets. Space ` ` separated for multiple values.
Each url will be accessible using the file name as a key. Any snippets within the files will be extracted and accessible as individual keyed snippets.
```ps
mdsnippets --urls-as-snippets "https://github.com/SimonCropp/MarkdownSnippets/snippet.cs"
```
```ps
mdsnippets -u "https://github.com/SimonCropp/MarkdownSnippets/snippet.cs"
```
## Using Snippets
The keyed snippets can be used in any documentation `.md` file by adding the text `snippet: KEY`.
Then snippets with that key.
For example
Some blurb about the below snippet
snippet: MySnippetName
The resulting markdown will be:
Some blurb about the below snippet
```
My Snippet Code
```
snippet source | anchor
Notes:
* The vertical bar ( | ) is used to separate adjacent links as per web accessibility recommendations: https://webaim.org/techniques/hypertext/hypertext_links#groups
* [H33: Supplementing link text with the title attribute](https://www.w3.org/TR/WCAG20-TECHS/H33.html)
### Including a snippet from the web
Snippets that start with `http` will be downloaded and the contents rendered. For example:
snippet: https://raw.githubusercontent.com/SimonCropp/MarkdownSnippets/master/license.txt
Will render:
```txt
The MIT License (MIT)
...
```
anchor
Files are downloaded to `%temp%MarkdownSnippets` with a maximum of 100 files kept.
### Including a full file
If no snippet is found matching the defined name. The target directory will be searched for a file matching that name. For example:
snippet: license.txt
Will render:
```txt
The MIT License (MIT)
...
```
anchor
### LinkFormat
Defines the format of `snippet source` links that appear under each snippet.
#### Command line
```ps
mdsnippets --link-format Bitbucket
```
```ps
mdsnippets -l Bitbucket
```
#### Values
```cs
namespace MarkdownSnippets;
public enum LinkFormat
{
GitHub,
Tfs,
Bitbucket,
GitLab,
DevOps,
None
}
```
snippet source | anchor
Link format `None` will omit the source link but still keep the snippet anchor.
### OmitSnippetLinks
The links below a snippet can be omitted.
#### Command line
```ps
mdsnippets --omit-snippet-links true
```
#### Config file
```
{
"OmitSnippetLinks": true
}
```
#### How links are constructed
```cs
switch (linkFormat)
{
case LinkFormat.GitHub:
Polyfill.Append(builder, $"{path}#L{snippet.StartLine}-L{snippet.EndLine}");
return;
case LinkFormat.Tfs:
Polyfill.Append(builder, $"{path}&line={snippet.StartLine}&lineEnd={snippet.EndLine}");
return;
case LinkFormat.Bitbucket:
Polyfill.Append(builder, $"{path}#lines={snippet.StartLine}:{snippet.EndLine}");
return;
case LinkFormat.GitLab:
Polyfill.Append(builder, $"{path}#L{snippet.StartLine}-{snippet.EndLine}");
return;
case LinkFormat.DevOps:
Polyfill.Append(builder, $"?path={path}&line={snippet.StartLine}&lineEnd={snippet.EndLine}&lineStartColumn=1&lineEndColumn=999");
return;
case LinkFormat.None:
throw new($"Unknown LinkFormat: {linkFormat}");
}
```
snippet source | anchor
### UrlPrefix
UrlPrefix allows a string to be defined that will prefix all snippet links. This is helpful when the markdown file are being hosted on a site that is not co-located with the source code files. It can be defined in the [config file](/docs/config-file.md), the [MsBuild task](/docs/msbuild.md), and the dotnet tool.
#### Command line
```ps
mdsnippets --url-prefix "TheUrlPrefix"
```
#### Config file
```
{
"UrlPrefix": "TheUrlPrefix"
}
```
## Add to Windows Explorer
Use [src/context-menu.reg](context-menu.reg) to add MarkdownSnippets to the Windows Explorer context menu.
```reg
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\Shell]
@="none"
[HKEY_CLASSES_ROOT\Directory\shell\mdsnippets]
"MUIVerb"="run mdsnippets"
"Position"="bottom"
[HKEY_CLASSES_ROOT\Directory\Background\shell\mdsnippets]
"MUIVerb"="run mdsnippets"
"Position"="bottom"
[HKEY_CLASSES_ROOT\Directory\shell\mdsnippets\command]
@="cmd.exe /c mdsnippets \"%V\""
[HKEY_CLASSES_ROOT\Directory\Background\shell\mdsnippets\command]
@="cmd.exe /c mdsnippets \"%V\""
```
snippet source | anchor
## More Documentation
* Developer Information
* [.net API](/docs/api.md)
* [MsBuild Task](/docs/msbuild.md)
* [Github Action](/docs/github-action.md)
* Customisation
* [Config file convention](/docs/config-file.md)
* [Max Width](/docs/max-width.md)
* [Includes](/docs/includes.md)
* [Directory Exclusion](/docs/exclusion.md)
* [Header](/docs/header.md)
* Writing Documentation
* [Indentation](/docs/indentation.md)
* [Table of contents](/docs/toc.md)
## Credits
Loosely based on some code from https://github.com/shiftkey/scribble.
## Icon
[Down](https://thenounproject.com/AlfredoCreates/collection/arrows-5-glyph/) by [Alfredo Creates](https://thenounproject.com/AlfredoCreates) from [The Noun Project](https://thenounproject.com/).