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(eslint-plugin): remove support for eslint 5 #2683

Merged
merged 5 commits into from
Aug 22, 2021

Conversation

thomasmichaelwallace
Copy link
Contributor

Resolves #2465

As far as I understood the issue, you don't think this is a breaking change (what with v5 being very old).

Following the issue I compared against eslint 6.8 (latest) to see what messageIds weren't set then, so as to avoid regressing #2451.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @thomasmichaelwallace!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@bradzacher
Copy link
Member

Thanks for doing this!

I didn't label it as such, but it is a breaking change - any change in the supported dependencies is a breaking change (even if people should have upgraded their deps by now).
We can leave this on ice until we are ready for the next major.

@bradzacher bradzacher added this to the 5.0.0 milestone Oct 16, 2020
@bradzacher bradzacher added breaking change This change will require a new major version to be released dependencies Issue about dependencies of the package labels Oct 16, 2020
@thomasmichaelwallace
Copy link
Contributor Author

No worries - I did suspect as much. Feel free to @thomasmichaelwallace me when the time comes for v5, I'd be happy to tackle any issues updating the branch for merge.

It'd be awesome if you could label the PRs hacktoberfest-accepted in the interim. (Sorry to ask, it's annoying they put this on the maintainers; if it's a hassle, it's not a problem.)

@armano2
Copy link
Member

armano2 commented Feb 8, 2021

we should also look at changes done in #2917 and most likely some of them can be removed, that could potentially partially fix #2279

@bradzacher
Copy link
Member

Unfortunately with eslint v8 they hid all of their utils - so we can't leverage them - so we're stuck with the changes from #2917

Copy link
Member

@bradzacher bradzacher left a comment

Choose a reason for hiding this comment

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

thanks for this! we can finally merge this in :)

@bradzacher bradzacher merged commit 207a231 into typescript-eslint:v5 Aug 22, 2021
@thomasmichaelwallace thomasmichaelwallace deleted the issue-2465 branch August 22, 2021 21:55
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking change This change will require a new major version to be released dependencies Issue about dependencies of the package hacktoberfest-accepted
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Drop support for ESLint v5
3 participants