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

fix(eslint-plugin): [no-unsafe-member-access] report on only the accessed property #7717

Conversation

Josh-Cena
Copy link
Member

PR Checklist

Overview

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @Josh-Cena!

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.

@netlify
Copy link

netlify bot commented Oct 2, 2023

Deploy Preview for typescript-eslint failed.

Name Link
🔨 Latest commit 130a11a
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/651ae8691cc3ac00081fc819

Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Oh dear heavens yes this has bugged me for the longest time 🙏

@JoshuaKGoldberg JoshuaKGoldberg merged commit f81a2da into typescript-eslint:main Oct 11, 2023
42 of 47 checks passed
@Josh-Cena Josh-Cena deleted the unsafe-member-access-report-range branch October 11, 2023 15:56
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 19, 2023
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.

[no-unsafe-member-access] location of warning is swamping other warnings
2 participants