Moving Feature Refactorings
Overview
Use this family after evidence identifies a fitting structural transformation. Apply one primary technique at a time and verify immediately.
Procedure
- Confirm the selected technique and its preconditions in Moving Feature Refactorings.
- Record affected behavior and a diff budget.
- Apply only the selected technique's smallest viable step.
- Verify the step before composing another transformation.
- Stop and reassess when public contracts, lifecycle, state identity, or actual scope exceed expectations.
Quick Reference
The family reference contains 9 canonical techniques with intent, signals, avoid conditions, mechanics, preservation checkpoints, smell links, composition hints, JavaScript/TypeScript notes, React/Vue notes, adaptation guidance, and original frontend examples.
Common Mistakes
- Choosing a technique by name without checking its preconditions.
- Combining several structural intentions in one diff.
- Assuming a classical class-based form is mandatory in modern frontend code.
- Treating passing tests as proof when the relevant behavior is not covered.