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
fix!: Parsing 'exported' comment using parseListConfig #17675
Conversation
✅ Deploy Preview for docs-eslint canceled.
|
@amondev thanks so much for contributing. I think we need to decide on this point before proceeding: #17622 (comment) |
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
refer #17622 (comment). |
FYI) Now updating this PR with @amondev , sorry for late! 🙇 |
I converted this PR to draft, as we keep breaking changes as drafts for now. |
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.
The code changes look good to me.
Can you also add some tests to confirm the new behavior?
/* exported foo, bar */
- should mark both variables./* exported foo bar */
- shouldn't mark any./* esported foo: true
*/ - also shouldn't mark.
Tests for SourceCode
could be after this one, tests for Linter eslintrc mode inside this describe, test for Linter flat config mode inside this describe.
@mdjermanovic Thank you for your comment! I'll attempt to add a test. |
@mdjermanovic I updated PR! 😄 |
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
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.
LGTM. Waiting for @mdjermanovic to verify his suggestions.
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.
LGTM, thanks for contributing!
* main: chore: use jsdoc/no-multi-asterisks with allowWhitespace: true (eslint#17900) chore: fix getting scope in tests (eslint#17899) fix!: Parsing 'exported' comment using parseListConfig (eslint#17675) docs: updated examples of `max-lines` rule (eslint#17898) feat!: Remove valid-jsdoc and require-jsdoc (eslint#17694)
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain:
Parsing 'exported' comment using parseListConfig.
Fixes #17622.
What changes did you make? (Give an overview)
In the docs, only information about the name entries.
However, when processing
/* exported */
comments, Linter usesparseStringConfig
function, making it appear as if it's checking thename: value
entries.So, change Linter to use the
parseListConfig
function for parsing/* exported */
comments.Is there anything you'd like reviewers to focus on?