Principle Migrate Callers Then Delete Legacy Apis

Move callers to the new shape and delete the old path in the same migration wave instead of carrying a compatibility layer. Use when when replacing an internal api.

TheOnlyFusionCube Updated

File contents

Migrate Callers Then Delete Legacy APIs

Trigger

When replacing an internal API.

Rule

Move callers to the new shape and delete the old path in the same migration wave instead of carrying a compatibility layer.

Application

  1. Name the concrete decision this principle changes.
  2. Apply the rule to that decision, not as a decorative citation.
  3. Prefer evidence from the current repository/runtime over generic preference.
  4. If the principle conflicts with an explicit user constraint, keep the constraint and state the tradeoff.

TheOnlyFusionCube/potetos-for-everyone/tree/main/skills/principle-migrate-callers-then-delete-legacy-apis commit 69d1e5822f

Frequently asked questions

npx skillmds@latest add theonlyfusioncube/principle-migrate-callers-then-delete-legacy-apis