PHP 8.2 Dynamic Properties and Visibility Transition

PHP 8.2 deprecates the creation of dynamic properties unless the class is explicitly marked with the #[AllowDynamicProperties] attribute. This change aims to prevent accidental public access and state mutation caused by typos or undeclared class members.

When transitioning a codebase from PHP 7.x or 8.0 to 8.2, developers must decide between declaring properties with specific visibility modifiers (private, protected, or public) or utilizing the attribute to maintain legacy behavior. However, the interaction between these visibility constraints and the deprecation warning creates uncertainty during the migration of large inheritance chains.

What is the recommended strategy for handling undeclared properties in a base class to ensure child classes do not trigger deprecation warnings without exposing the entire object to public dynamic mutation? Does the #[AllowDynamicProperties] attribute override the strict encapsulation goals of visibility modifiers?