[sam-parsons]

Summary

• Added configured function-call stripping for standalone expression statements via functions option matching.
• Supports dotted call targets like console.log and logger.debug.
• Preserves non-target calls and inline call expressions, keeping issue scope focused.

Issues

• Fixes Issue C: Strip configured function-call expression statements #3 — Strip configured function-call expression statements
• Refs Issue E: Handle chained-call strip edge cases safely #5 — chained-call safety remains for dedicated handling

How to test

• npm run check
• npm run build

Notes

• Current implementation is regex-based and intentionally scoped to line-based standalone calls; AST-based handling and chain safety are tracked in later issues.

---

Learning notes

Scope-first implementation to avoid cross-issue coupling

What it is
Scope-first implementation means shipping one clearly bounded behavior per issue, even when you can see adjacent improvements. It keeps review size small and prevents hidden coupling between features.

Where it appears in this PR
src/index.ts adds stripConfiguredCallExpressions() for standalone configured calls, while explicitly leaving chain-edge handling out of this change.

Why it was the right call here
The alternative was combining call stripping with chained-call safety and map-generation refactors in one PR. That would increase risk and make regressions harder to attribute. By separating concerns, this PR validates core matching semantics first, and later issues can focus on correctness edges with targeted tests.

If you want to go deeper
Search: "incremental architecture" and "small batch size in code review".