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.

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

Chore: avoid using legacy report API in no-irregular-whitespace #11013

Merged
merged 1 commit into from Oct 24, 2018

Conversation

not-an-aardvark
Copy link
Member

What is the purpose of this pull request? (put an "X" next to item)

[x] Other, please explain:

What changes did you make? (Give an overview)

This updates the no-irregular-whitespace rule to avoid using the legacy multi-argument context.report API. We have a linting rule to enforce against using the API, but the rule wasn't enforcing it in this case.

This was originally found by @aladdin-add in eslint-community/eslint-plugin-eslint-plugin#64.

Is there anything you'd like reviewers to focus on?

Nothing in particular

@not-an-aardvark not-an-aardvark added the chore This change is not user-facing label Oct 24, 2018
This updates the no-irregular-whitespace rule to avoid using the legacy multi-argument `context.report` API. We have a linting rule to enforce against using the API, but the rule wasn't enforcing it in this case.

This was originally found by Aladdin-ADD in eslint-community/eslint-plugin-eslint-plugin#64.
@not-an-aardvark not-an-aardvark merged commit 3d88b38 into master Oct 24, 2018
@not-an-aardvark not-an-aardvark deleted the no-use-legacy-report-api branch October 24, 2018 21:37
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Apr 23, 2019
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Apr 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants