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

feat(eslint-plugin): more optional chain support in rules #1363

Merged
merged 2 commits into from Dec 21, 2019

Conversation

bradzacher
Copy link
Member

See #1051

This finishes off the "easy" rules

@bradzacher bradzacher added the enhancement New feature or request label Dec 20, 2019
@typescript-eslint
Copy link
Contributor

Thanks for the PR, @bradzacher!

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 bradzacher mentioned this pull request Dec 20, 2019
25 tasks
@bradzacher bradzacher changed the title feat(eslint-plugin): optional chain support [unbound-method][require-array-sort-compare] feat(eslint-plugin): more optional chain support in rules Dec 21, 2019
@bradzacher bradzacher merged commit 3dd1b02 into master Dec 21, 2019
@bradzacher bradzacher deleted the optional-chain-support-3 branch December 21, 2019 04:20
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant