Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Utilize warnIgnored instead of filtering messages #915

Merged
merged 1 commit into from
May 22, 2017

Conversation

Arcanemagus
Copy link
Member

Now that all execution of ESLint is being done through executeOnText we can move to the warnIgnored option instead of manually filtering out the ignore messages.

Fixes #900.

Now that all execution of ESLint is being done through `executeOnText`
we can move to the `warnIgnored` option instead of manually filtering
out the ignore messages.

Fixes #900.
Copy link
Member

@IanVS IanVS left a comment

Choose a reason for hiding this comment

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

Much better!

@Arcanemagus Arcanemagus merged commit bb5321b into master May 22, 2017
@Arcanemagus Arcanemagus deleted the arcanemagus/warn-ignored branch May 22, 2017 16:44
@Arcanemagus
Copy link
Member Author

Turns out this was entirely wrong. The option has no meaning there and needed to be passed in as a third argument to executeOnText, not as an argument to CLIEngine.

The reason we never saw that this wasn't working is that the default behavior was fixed to be what you would expect anyway in eslint/eslint#6632.

Arcanemagus added a commit that referenced this pull request Jan 7, 2018
This flag has no meaning to the `CLIEngine` constructor, it is only
valid as an optional third argument to `executeOnText`. When this was
mistakenly added in #915
this was missed. Luckily the problem it was meant to solve was accepted
as a bug against ESLint itself and fixed there which is why this wasn't
caught earlier.
Arcanemagus added a commit that referenced this pull request Jan 15, 2018
This flag has no meaning to the `CLIEngine` constructor, it is only
valid as an optional third argument to `executeOnText`. When this was
mistakenly added in #915
this was missed. Luckily the problem it was meant to solve was accepted
as a bug against ESLint itself and fixed there which is why this wasn't
caught earlier.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants