What should I do before modifying a class component?
Read its lifecycle methods and state flow first. Class components scatter logic across methods, so take time to understand how state and effects interact before changing anything. Understanding before changing prevents bugs.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Best Practices for Working With React Class Components in Legacy Code
No. If a class component works and is not changing, leave it. Rewriting working code introduces risk without value. Convert when you are already modifying a component for another reason, so you modernize incrementally.
When you are already touching the component for a feature or bug fix. Convert it at the same time so you modernize the codebase incrementally without a risky big-bang rewrite. Avoid converting stable, untouched components.
Preserve behavior exactly. Map lifecycle methods to useEffect carefully, get the dependency array right, and test that the converted component behaves identically to the original. Use the hooks lint plugin to catch dependency mistakes.
Still have questions?
Browse all our FAQs or reach out to our support team