Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
remark-lint-fenced-code-marker
Advanced tools
remark-lint rule to warn when fenced code markers violate the given style
Warn for violating fenced code markers.
Options: '`'
, '~'
, or 'consistent'
, default: 'consistent'
.
'consistent'
detects the first used fenced code marker style and warns
when subsequent fenced code blocks use different styles.
remark-stringify
formats fences using '`'
(grave accent) by default.
Pass
fence: '~'
to use ~
(tilde) instead.
See Using remark to fix your Markdown on how to automatically fix warnings for this rule.
This rule is included in the following presets:
Preset | Setting |
---|---|
remark-preset-lint-consistent | 'consistent' |
remark-preset-lint-markdown-style-guide | '`' |
ok.md
Indented code blocks are not affected by this rule:
bravo();
No messages.
not-ok-consistent-tick.md
```alpha
bravo();
```
~~~
charlie();
~~~
5:1-7:4: Fenced code should use `` ` `` as a marker
not-ok-consistent-tilde.md
~~~alpha
bravo();
~~~
```
charlie();
```
5:1-7:4: Fenced code should use `~` as a marker
ok.md
When configured with '`'
.
```alpha
bravo();
```
```
charlie();
```
No messages.
ok.md
When configured with '~'
.
~~~alpha
bravo();
~~~
~~~
charlie();
~~~
No messages.
not-ok-incorrect.md
When configured with '💩'
.
1:1: Incorrect fenced code marker `💩`: use either `'consistent'`, `` '`' ``, or `'~'`
npm:
npm install remark-lint-fenced-code-marker
You probably want to use it on the CLI through a config file:
…
"remarkConfig": {
"plugins": [
…
"lint",
+ "lint-fenced-code-marker",
…
]
}
…
Or use it on the CLI directly
remark -u lint -u lint-fenced-code-marker readme.md
Or use this on the API:
var remark = require('remark')
var report = require('vfile-reporter')
remark()
.use(require('remark-lint'))
+ .use(require('remark-lint-fenced-code-marker'))
.process('_Emphasis_ and **importance**', function (err, file) {
console.error(report(err || file))
})
See contributing.md
in remarkjs/.github
for ways
to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
FAQs
remark-lint rule to warn when fenced code markers violate the given style
The npm package remark-lint-fenced-code-marker receives a total of 70,168 weekly downloads. As such, remark-lint-fenced-code-marker popularity was classified as popular.
We found that remark-lint-fenced-code-marker demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.