Explore PHP 8.4's Asymmetric Visibility feature in detail, redefining access control for getters and setters with enhanced flexibility and security.

Mohammed Samgan Khan

Application Security

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

PHP 8.4 introduces a unique feature known as Asymmetric Visibility, allowing different read and write access levels for class properties. This feature enhances encapsulation by permitting properties to be read publicly while restricting write access to the class or its subclasses. Traditional visibility levels like Public, Private, and Protected are also discussed. The syntax and crucial rules for implementing Asymmetric Visibility are outlined, emphasizing its exclusive availability in PHP 8.4 and later versions.

Php 8.4 Asymmetric Visibility Explained In Detail

I see text article in white, on a white page…cant read it :
<img src="https://media.daily.dev/image/upload/s--8oRCRX5h--/f_auto/v1732611991/ugc/content_33324ad7-3cb5-4090-b870-1a63159e034e" alt="image">

This should never have been implemented. It sounds like a total mess :|

Only this “private(set)” which is totally unnecessary, messed up the syntax. Only “public private $…” was necessary.