Hi Dmytro Thanks for your proposal. This seems like a reasonable use of attributes.
On Mon, Oct 6, 2025 at 12:16 AM Dmytro Kulyk <[email protected]> wrote: > > This proposal introduces a new attribute, #[NoSerialize], that can be > applied to class properties to explicitly exclude them from > serialization when using PHP’s built-in serialization mechanisms. A few things: * How does this interact with inheritance, i.e. is this flag inherited to overridden child properties? I would assume no, as with other attributes. But it would be good to spell it out. * There are other forms of serialization, most notably JSON and var_export(). Are these affected in any way? Does it make sense to have a universal solution? * There may also be a benefit to marking classes as entirely not serializable, which would throw when encountering the class during [un]serialization. We have some of those internally. [^1] Ilija [^1]: https://github.com/search?q=repo%3Aphp%2Fphp-src%20%40not-serializable&type=code
