-
Notifications
You must be signed in to change notification settings - Fork 188
JS-548 Make parser
and parserOptions
visible in rules
#5094
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
Conversation
parser
and parserOptions
visible in rulesparser
and parserOptions
visible in rules
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.
Just cosmetic comments from my side. 👌
@@ -81,7 +81,7 @@ function analyzeFile(linter: LinterWrapper, extendedSourceCodes: ExtendedSourceC | |||
|
|||
function analyzeSnippet(linter: LinterWrapper, extendedSourceCode: ExtendedSourceCode) { | |||
const { issues, ucfgPaths } = linter.lint( | |||
extendedSourceCode.sourceCode, | |||
extendedSourceCode, |
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.
should this be also renamed?
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.
done
packages/jsts/tests/tools/testers/comment-based/helpers/comments.ts
Outdated
Show resolved
Hide resolved
|
JS-548
We need to have the parser and parserOptions available to be able to implement ESLINTJS-60