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: make parse() a pure function in Linter (refs #9161) #9183

Merged
merged 1 commit into from Aug 30, 2017

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 refactors the private parse function in linter.js to be a pure function. Instead of adding an error to a provided messages array, it now returns an object with a boolean success property. It also handles extracting parserServices when parseForESLint is used, which simplifies the logic in the Linter#verify method a bit.

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 Aug 30, 2017
@eslintbot
Copy link

LGTM

@mention-bot
Copy link

@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @gyandeeps, @nzakas and @mysticatea to be potential reviewers.

@eslintbot
Copy link

LGTM

Copy link
Member

@gyandeeps gyandeeps left a comment

Choose a reason for hiding this comment

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

Nice update.
I hope freeze won't hurt perf as previously we have seen some perf issue with it.

@eslintbot
Copy link

LGTM

@not-an-aardvark not-an-aardvark merged commit 4b94c6c into master Aug 30, 2017
@not-an-aardvark not-an-aardvark deleted the parse-pure branch August 30, 2017 18:56
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 27, 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 Feb 27, 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

4 participants