migrate-static-to-wrapper

To refactor static DateTime calls to TimeProvider, mechanically replace call sites like DateTime.UtcNow with TimeProvider.GetUtcNow(), add constructor injection for the dependency, and update DI registration and tests to verify the solution builds.

Replacing File and Directory static calls involves converting them to IFileSystem equivalents for safer, mockable filesystem access. The process adds constructor injection, updates using directives, and verifies DI registration within a bounded code scope.

Yes, you can migrate static dependencies incrementally across a single namespace. The refactoring applies mechanical codemod-style replacements to a bounded code scope, targeting one file, project, or namespace at a time to ensure safe transitions.

Migrating static dependency call sites improves code testability by replacing hard-coded static dependencies with injected wrappers or built-in abstractions, allowing you to mock filesystem access and control time during deterministic testing.

Yes, you must update dependency injection registration when refactoring static calls. Adding constructor or ambient injection for new abstractions requires updating DI registration expectations to successfully resolve dependencies and verify the build.