docs(linter): update no-unsafe-type-assertion to reflect correct rule behavior

[camc314]

Fixes oxc-project/tsgolint#492

[camc314]

• docs(linter): update no-unsafe-type-assertion to reflect correct rule behavior #16646 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

This PR updates the documentation for the no-unsafe-type-assertion TypeScript linter rule to accurately reflect its intended behavior. The previous documentation incorrectly described the rule as disallowing type assertions using any, but the rule actually disallows type assertions that narrow types (which can bypass TypeScript's type-checking).

Key Changes

• Updated rule description to focus on type narrowing rather than any types
• Replaced all code examples to demonstrate narrowing vs. broadening type assertions
• Clarified that broadening type assertions are safe while narrowing ones are unsafe

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codspeed-hq]

CodSpeed Performance Report

Merging #16646 will not alter performance

_{Comparing c/12-09-docs_linter_update_no-unsafe-type-assertion_to_reflect_correct_rule_behavior (dc793ad) with main (6cddbe7)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

1. No successful run was found on main (dc793ad) during the generation of this report, so 6cddbe7 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[graphite-app]

Merge activity

• Dec 9, 12:25 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Dec 9, 12:30 PM UTC: Merged by the Graphite merge queue.