Skip to content

Conversation

@OleksandraKordonets
Copy link
Contributor

PR Checklist

Overview

Extend isUnsafeAssignment to walk object types structurally with cycle guards and early exits, so nested any in object arguments, unions, tuples, arrays, and index signatures are detected even when shapes are inline or via aliases, not only when the generic bases match. This aligns with the goal of the no-unsafe rules to catch any flowing through call sites and assignments, and it expands on the helper’s current simple top level behavior. All no-unsafe rules that call the helper benefit, including no-unsafe-argument, no-unsafe-assignment, and, by extension, related rules that rely on the same type-level check, the generic fast path remains for identical bases while inline shapes now flag, and no-unsafe-assignment suppresses a duplicate top level diagnostic when a nested property already errors.

Tests cover shallow and nested objects in packages/type-utils/tests/isUnsafeAssignment.test.ts plus the issue’s repro in packages/eslint-plugin/tests/rules/no-unsafe-argument.test.ts, a small website config tweak avoids spreading any to satisfy the stricter checks, and performance is guarded with early exits, default lib skipping, and cycle tracking.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @OleksandraKordonets!

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 Dec 10, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit b669595
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/693b703084f82a00080c79fe
😎 Deploy Preview https://deploy-preview-11834--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 97 (no change from production)
Accessibility: 97 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@nx-cloud
Copy link

nx-cloud bot commented Dec 10, 2025

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

To disable these notifications, a workspace admin can disable them in workspace settings.


View your CI Pipeline Execution ↗ for commit b669595

Command Status Duration Result
nx run-many -t lint ❌ Failed 3m 20s View ↗
nx test eslint-plugin --coverage=false ✅ Succeeded 5m 8s View ↗
nx run-many -t typecheck ✅ Succeeded 2m 10s View ↗
nx test eslint-plugin-internal --coverage=false ✅ Succeeded 10s View ↗
nx test typescript-estree --coverage=false ✅ Succeeded 2s View ↗
nx run types:build ✅ Succeeded 2s View ↗
nx run integration-tests:test ✅ Succeeded 3s View ↗
nx run generate-configs ✅ Succeeded 5s View ↗
Additional runs (29) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-12-12 01:43:26 UTC

@codecov
Copy link

codecov bot commented Dec 10, 2025

Codecov Report

❌ Patch coverage is 90.00000% with 22 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.54%. Comparing base (dd96947) to head (b669595).

Files with missing lines Patch % Lines
packages/type-utils/src/isUnsafeAssignment.ts 89.62% 22 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##             main   #11834    +/-   ##
========================================
  Coverage   90.53%   90.54%            
========================================
  Files         523      523            
  Lines       53096    53311   +215     
  Branches     8838     8897    +59     
========================================
+ Hits        48073    48268   +195     
- Misses       5010     5030    +20     
  Partials       13       13            
Flag Coverage Δ
unittest 90.54% <90.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...es/eslint-plugin/src/rules/no-unsafe-assignment.ts 97.57% <100.00%> (+0.04%) ⬆️
packages/typescript-estree/src/convert.ts 30.89% <100.00%> (ø)
packages/type-utils/src/isUnsafeAssignment.ts 90.42% <89.62%> (-0.12%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@OleksandraKordonets
Copy link
Contributor Author

@JoshuaKGoldberg
Hi, I wanted to ask for some guidance on the CI lint failures here.
Earlier I fixed the lint errors for this branch in commit 1d01bd4, but after I added tests, the lint job started failing again. I can fix these, but it would mean touching extra files outside the core of this PR. Before I do that, I wanted to ask what you prefer. Should I keep this PR focused on my solution and leave the other lint issues for a follow up, or is it ok to include those extra lint fixes here so CI passes? I want to follow the project style and avoid unnecessary changes, so any guidance would be very helpful. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enhancement: [no-unsafe-*] check anys nested inside object arguments

1 participant