Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129015
Precedence: list
MIME-Version: 1.0
Date: Fri, 31 Oct 2025 09:44:07 +0100
To: Dmytro Kulyk <lnkvisitor.ts@gmail.com>
Cc: Ilija Tovilo <tovilo.ilija@gmail.com>, PHP internals
 <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC][Discussion] Add #[NoSerialize] attribute for
 excluding properties or classes from serialization
In-Reply-To: <CAPqq82vPdraqE1DuJQ6w4pWpwr1koTHcj_o0pKV1dXxRoaguqg@mail.gmail.com>
References: <CAPqq82sqFy1y77XLu8Kbncg18WNopeJdPrfB+JQ8FWNZ4XpTQg@mail.gmail.com>
 <CAPyj-LBG0nR75AUMXT0XCnpNnPP=T62NYvRQ34yeZpd+i=cTPw@mail.gmail.com>
 <CAPqq82sy1O9-J4yhvcPvsob3Rjdi1wFDW_t597850sBTbKc=sg@mail.gmail.com>
 <4b6abc36d8ab6cd306e95141869db3b0@bastelstu.be>
 <CAPqq82u7xhMDqmwuhEPOGqHdnrM3S2OM+HG=XpG-SyKPS3LofA@mail.gmail.com>
 <21ff8dee5016a1b7ecc412c44233abd1@bastelstu.be>
 <CAPqq82vPdraqE1DuJQ6w4pWpwr1koTHcj_o0pKV1dXxRoaguqg@mail.gmail.com>
Message-ID: <3a20b5ef66fc23de6bad022685b41190@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-10-30 23:24, schrieb Dmytro Kulyk:
> If we go in that direction, I’d suggest keeping the name
> #[NoSerialize], because it’s more general and clearly describes the
> action rather than the failure mode.
> #[NotSerializable] reads more like an error state, while
> #[NoSerialize] works naturally for both contexts — skipping properties
> silently and preventing class serialization (by throwing).
> 
> This way, the attribute name remains short and declarative, while the
> actual behavior (throwing vs skipping) can be determined by where it’s
> applied — on a class or on a property — without introducing another
> attribute.

That makes sense to me and I don't have a suggestion for a better name.

Best regards
Tim Düsterhus