fix(eslint-plugin): [prefer-nullish-coalescing] handle intersected primitive types #9378
Conversation
|
Thanks for the PR, @jakebailey! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 71ec3ed. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
JoshuaKGoldberg
added
the
1 approval
JoshuaKGoldberg
merged commit 23e6468
into
typescript-eslint:main
PR Checklist
Overview
For a union like
string & { __brand?: any } | undefined, treat the intersection like a primitive; this helps cases like brandedPathtypes.