Principle Migrate Callers Then Delete Legacy Apis

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

arjitj2 Updated 16 repo stars

File contents

Migrate Callers Then Delete Legacy APIs

  • Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details

When this applies:

  • No external users depend on backward compatibility
  • The project can absorb coordinated breaking changes
  • The new API is part of a simplification or refactor initiative

arjitj2/open-pstack commit 4fc3dc0b98

Frequently asked questions

npx get-skill add arjitj2/principle-migrate-callers-then-delete-legacy-apis