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 handling rules instances in config-validator #9364

Merged
merged 2 commits into from Nov 10, 2017

Conversation

not-an-aardvark
Copy link
Member

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

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make? (Give an overview)

This is a modified version of #9277, which was merged but then reverted later for performance reasons. The performance issues from #9177 have been fixed (Linter no longer creates a new map of rules whenever it lints text).

The goal of this change is to progress towards being able to remove the rules property from Linter instances. Unfortunately, this isn't possible yet, since there are a few other modules that rely on reading the list of defined rules.

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 Sep 27, 2017
@eslintbot
Copy link

LGTM

Copy link
Member

@ilyavolodin ilyavolodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind, saw the link to the original issue.

@not-an-aardvark
Copy link
Member Author

The goal of this change is to progress towards being able to remove the rules property from Linter instances. This property is not supposed to be part of the public Linter API, but there are other parts of core using it, so we can't remove it yet.

@ilyavolodin
Copy link
Member

Just to clarify, when you are talking about rules property you mean linter.rules, right? linter.getRules() will still be available?

@not-an-aardvark
Copy link
Member Author

Yes, that's correct.

@ilyavolodin
Copy link
Member

@not-an-aardvark Could you rebase please?

This is a modified version of #9277, which was merged but then reverted later for performance reasons. The performance issues from #9177 have been fixed (`Linter` no longer creates a new map of rules whenever it lints text).

The goal of this change is to progress towards being able to remove the `rules` property from `Linter` instances. Unfortunately, this isn't possible yet, since there are a few other modules that rely on reading the list of defined rules.
@not-an-aardvark not-an-aardvark merged commit 4def876 into master Nov 10, 2017
@not-an-aardvark not-an-aardvark deleted the reduce-rules-access branch November 10, 2017 07:57
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators May 10, 2018
@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 May 10, 2018
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

3 participants