AST migration removed test-file exemption for unsafe_type_assertion #26

Activity

1. coderabbitai commented on Jul 27, 2026

   

   coderabbitaibot

   on Jul 27, 2026 – with coderabbitai

   More actions

   🔗 Related PRs

   #9 - fix: resolve all false positives (issues #2, #6, #7, #8) [closed]
   #15 - feat: add positional path arguments for single-file/directory targeting [closed]
   #23 - feat: detect unsafe TypeScript type assertions via AST (issue #22) [open]
   #24 - feat: migrate unsafe_type_assertion from regex to AST detection [open]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
2. CodeDeficient commented on Jul 27, 2026

   

   CodeDeficient

   on Jul 27, 2026

   OwnerAuthor

   More actions

   Resolved by eef4363 — test-file exclusion for unsafe_type_assertion was restored via skipTests:true on the pattern definition. The scope is narrower than the pre-migration heuristic (uses standard isTestFile classification: .test., .spec., tests, mocks, test-) but the exemption itself is back. Validated by test at ai-slop-detector.behavior.test.ts:413-431.
3. CodeDeficient

   closed this as completedon Jul 27, 2026