Readonly properties should be assignable outside the constructor

[nafetsrybak]

Feature request

As Larry Garfield said
"Currently, phpstan complains about readonly properties that are not assigned in the constructor, or if they're assigned from elsewhere in the class.

While it's true that in many cases that's a code smell, there are also ample cases where this is entirely reasonable to do, even beneficial, and so these rules create false positives.

I believe these rules should be removed, or disable-able. (If they're already disableable and I don't see a flag for it, please advise on the flag.)"
Original issue: "#6562"

I have problems when I want do denormalize/deserialize data to my readonly DTO (request/response) classes for example using
https://symfony.com/doc/current/serializer.html#built-in-normalizers
PropertyNormalizer.php. They should not have any __construct. Would it be possible to add some "@" type annotation to disable this behavior for certain class?

Best regards Stefan

Did PHPStan help you today? Did it make you happy in any way?

No response

[ondrejmirtes]

If you show me an example on phpstan.org/try using readonly properties, I can most likely point out how your code can fail at runtime. That's why PHPStan decides to report this (I admin) quite opinionated rule.

I'm closing this in favour of there already being #7477, but you can still respond to this issue.

[ondrejmirtes]

Just to be complete - you can easily ignore related identifiers if you decide your code is fine.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.