Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add gap support #8

Closed
wooorm opened this issue Jun 9, 2015 · 0 comments
Closed

Add gap support #8

wooorm opened this issue Jun 9, 2015 · 0 comments
Labels
🗄 area/interface This affects the public interface 💪 phase/solved Post is done 🧒 semver/minor This is backwards-compatible change 🦋 type/enhancement This is great to have

Comments

@wooorm
Copy link
Member

wooorm commented Jun 9, 2015

I’m privately using mdast-lint in a workflow with other plug-ins, such as mdast-toc: a plug-in which generates content.

As outlined in the readme, those should be applied first. That’s because generated nodes of course do not have positional information. Thus, rules which only check a files contents, cannot white-list certain ranges.

However, by ignoring lines which are not available in the AST, those warnings can be hidden.
@wooorm wooorm closed this as completed in 136e760 Jun 29, 2015
@wooorm wooorm added ⛵️ status/released 🗄 area/interface This affects the public interface 🦋 type/enhancement This is great to have 🧒 semver/minor This is backwards-compatible change labels Aug 15, 2019
@wooorm wooorm added the 💪 phase/solved Post is done label Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🗄 area/interface This affects the public interface 💪 phase/solved Post is done 🧒 semver/minor This is backwards-compatible change 🦋 type/enhancement This is great to have
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wooorm