![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
remark-lint-ordered-list-marker-value
Advanced tools
Readme
Warn when the list item marker values of ordered lists violate a given style.
Options: 'single'
, 'one'
, or 'ordered'
, default: 'ordered'
.
When set to 'ordered'
, list item bullets should increment by one,
relative to the starting point.
When set to 'single'
, bullets should be the same as the relative starting
point.
When set to 'one'
, bullets should always be 1
.
remark-stringify
retains the number of the first list item bullet, and by default
increments the other items.
Pass
incrementListMarker: false
to not increment further list items.
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-markdown-style-guide | 'one' |
valid.md
The default value is `ordered`, so unless changed, the below
is OK.
1. Foo
2. Bar
3. Baz
Paragraph.
3. Alpha
4. Bravo
5. Charlie
Unordered lists are not affected by this rule.
* Anton
No messages.
valid.md
When configured with 'one'
.
1. Foo
1. Bar
1. Baz
Paragraph.
1. Alpha
1. Bravo
1. Charlie
No messages.
invalid.md
When configured with 'one'
.
1. Foo
2. Bar
2:1-2:8: Marker should be `1`, was `2`
also-invalid.md
When configured with 'one'
.
2. Foo
1. Bar
1:1-1:8: Marker should be `1`, was `2`
valid.md
When configured with 'single'
.
1. Foo
1. Bar
1. Baz
Paragraph.
3. Alpha
3. Bravo
3. Charlie
Paragraph.
0. Delta
0. Echo
0. Foxtrot
No messages.
valid.md
When configured with 'ordered'
.
1. Foo
2. Bar
3. Baz
Paragraph.
3. Alpha
4. Bravo
5. Charlie
Paragraph.
0. Delta
1. Echo
2. Foxtrot
No messages.
invalid.md
When configured with 'ordered'
.
1. Foo
1. Bar
2:1-2:8: Marker should be `2`, was `1`
invalid.md
When configured with 'invalid'
.
1:1: Invalid ordered list-item marker value `invalid`: use either `'ordered'` or `'one'`
npm:
npm install remark-lint-ordered-list-marker-value
You probably want to use it on the CLI through a config file:
...
"remarkConfig": {
"plugins": [
...
"lint",
+ "lint-ordered-list-marker-value",
...
]
}
...
Or use it on the CLI directly
remark -u lint -u lint-ordered-list-marker-value 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-ordered-list-marker-value'))
.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, organisation, or community you agree to abide by its terms.
FAQs
remark-lint rule to warn when the marker value of ordered lists violates a given style
We found that remark-lint-ordered-list-marker-value 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.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.