-
-
Notifications
You must be signed in to change notification settings - Fork 78
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.
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
New: making Plugin's Processor API chainable #1
Conversation
plugin-processors-chaining/README.md
Outdated
|
||
This feature will be implemented in `Linter#verify` method that is applying pre/post processes currently. Below is the implementation of [**verify**](https://github.com/eslint/eslint/blob/5da378ac922d732ca1765f08edee0face1b1b924/lib/linter.js#L1046) I imaged. | ||
|
||
(I'm sorry, I couldn't describe it in English.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry for not a hight-level description...
I updated this PR. |
Considering the following settings: // .eslintrc.js
module.exports = {
overrides: [
{
files: "*.md",
plugins: ["markdown"],
settings: {
markdown: {
targetBlocks: ["js", "ts", "html", "vue"]
}
}
},
{
files: "*.ts",
parser: "typescript-eslint-parser",
},
{
files: "*.html",
plugins: ["html"],
},
{
files: "*.vue",
plugins: ["vue"],
parser: "vue-eslint-parser",
},
]
} I expect the extracted blocks from Fortunately, we don't have to find |
Merged to #3. |
The first RFC 🎉
Summary
This proposal makes the processors being possible to combinate by that those preprocess can return the pair of code and filename. If the returned filename requires another processor, ESLint applies the processor recursively.
Related Issues