Release nan konbine ak Pou plis pase yon dekad, nou gen gouters ak setters religiously jere, gonfle entite nou yo ak DTOs ak boilerplate ki ajoute son vizyèl men nul valè biznis. PHP 8.4, Symfony 7.4 (LTS), avèk entwodiksyon an nan PHP 8.4 ak , nou ka finalman retire "Java-fikasyon" nan objè PHP. Nou ka ekri kout, modèl domèn ekspresif ki enkapsule konpòtman san yo pa verbosity la. Property Hooks Asymmetric Visibility Nan atik sa a, mwen pral eksplore ki jan yo modernize yon aplikasyon Symfony 7.4 lè l sèvi avèk karakteristik sa yo. Mwen pral refaktore yon entite doktrin style nan yon modèn, lean PHP 8.4 eleman, asire konpatibilite plen ak Serializer Symfony, Validator, ak Fòm. anviwònman Anvan nou plonje nan kòd la, tanpri asire w ke w ap kouri stack la kòrèk. Symfony 7.4 se vèsyon an Long-Term Support ki te lanse nan mwa Novanm 2025. Asire w ke anviwònman lokal ou se pare. Kòmanse lòd sa yo: php -v
# Output must indicate PHP 8.4.0 or higher

composer version
# Ensure you are on Composer 2.8+
 Nou pral itilize konpozan estanda Symfony 7.4. Si ou kòmanse yon nouvo pwojè: composer create-project symfony/skeleton:7.4.* my_project
cd my_project
composer require symfony/webapp-pack:7.4.*
composer require symfony/orm-pack
composer require symfony/serializer-pack
composer require symfony/validator-pack
 Si ou ap amelyore yon pwojè ki deja egziste, asire w ke restriksyon nan ak Pake nan . composer.json php ^8.4 symfony/* ^7.4 Asimetri vizibilite: fen a nan Getter / Setter boilerplate Pou ane sa yo, nou te fè pwopriyete prive ak ajoute chape piblik yo anpeche modifikasyon ekstèn, pandan y ap pèmèt aksè enteryè. The Old Way (PHP 8.3 and below): class User
{
    private string $email;

    public function __construct(string $email)
    {
        $this->email = $email;
    }

    public function getEmail(): string
    {
        return $this->email;
    }
    
    // No setter meant it was effectively "read-only" externally, 
    // but we still needed the getter to read it.
}
 : Vizibilite asimetrik pèmèt nou defini "pwodwi" pèmèt la indépendant de pèmèt la "kouvri". The PHP 8.4 Way class User
{
    // Publicly readable, but only writeable by the class itself (private)
    public private(set) string $email;

    public function __construct(string $email)
    {
        $this->email = $email;
    }
}
 Entegre ak doktrin Li travay san danje ak doktrin ORM nan Symfony 7.4. Doktrin sèvi ak refleksyon pou hidrate pwopriyete, elimine vizibilite garde, se konsa se konplètman an sekirite pou entitid mape. public private(set) Yon Entite Doktrin Modèn namespace App\Entity;

use Doctrine\ORM\Mapping as ORM;
use Symfony\Component\Validator\Constraints as Assert;

#[ORM\Entity]
class Product
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column]
    public private(set) ?int $id = null;

    #[ORM\Column(length: 255)]
    #[Assert\NotBlank]
    public private(set) string $name;

    #[ORM\Column]
    #[Assert\PositiveOrZero]
    public private(set) int $stock = 0;

    public function __construct(string $name)
    {
        $this->name = $name;
    }

    // Business logic method to mutate state
    public function addToStock(int $quantity): void
    {
        if ($quantity < 1) {
            throw new \InvalidArgumentException('Quantity must be positive');
        }
        $this->stock += $quantity;
    }
}
 Why this matters: 
 
 
 
 Zero Boilerplate: No getId(), getName(), getStock(). Safe Encapsulation: $product->stock = 100 trigger yon erè fatal soti nan deyò nan klas la. Ou dwe sèvi ak addToStock(), egzekite règ yo biznis ou. DX (Developer Experience): Autocompletion travay dirèkteman sou pwopriyete ($product->nom), ki santi pi "natif" pase metòd apèl. Property Hooks: pwopriyete entelijan Kòm Asymmetric Vizibilite kontwole nan pèmèt nou kontwole konpòtman. Yo ranplase metòd magik (__get, __set) ak eksplisit getters / setters ak logik ki anrejistre dirèkteman nan pwopriyete a. access Property Hooks Done Normalization (Sèt kouvèti) Imajine yon entite itilizatè kote imèl la dwe toujou anbake nan lavni. namespace App\Entity;

use Doctrine\ORM\Mapping as ORM;

#[ORM\Entity]
class User
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column]
    public private(set) ?int $id = null;

    #[ORM\Column(length: 180, unique: true)]
    public string $email {
        // The 'set' hook intercepts assignment
        set(string $value) {
            if (!filter_var($value, FILTER_VALIDATE_EMAIL)) {
                throw new \InvalidArgumentException("Invalid email format");
            }
            // The backing value is updated automatically via this assignment
            $this->email = strtolower($value);
        }
    }

    public function __construct(string $email)
    {
        // This triggers the set hook!
        $this->email = $email;
    }
}
 Verification: $user = new User('ADMIN@Example.com');
echo $user->email; // Outputs: admin@example.com
 Pwopriyete vityèl (The Get Hook) Pwopriyete vityèl pa sove done; yo calculate li sou flè. Sa a se pafè pou aksè atik konpetans nan Symfony DTOs oswa Entités ki pa bezwen yo dwe persiste nan baz done a. namespace App\Entity;

use Doctrine\ORM\Mapping as ORM;

#[ORM\Entity]
class Customer
{
    #[ORM\Column]
    public string $firstName;

    #[ORM\Column]
    public string $lastName;

    // This is a VIRTUAL property. It has no storage in memory.
    // Notice we do NOT add #[ORM\Column] because it's not in the DB.
    public string $fullName {
        get => $this->firstName . ' ' . $this->lastName;
    }
}
 Entegre ak Symfony Serializer Youn nan karakteristik ki pi fò nan Property Hooks nan Symfony 7.4 se ki jan serializer a konpoze yo. 
 
 
 Pwopriyete sipòte: Serialized nòmalman. Pwopriyete vityèl: Si yo piblik, Serializer trete yo menm jan ak pwopriyete reyèl. Ou pa bezwen plis #[SerializedName] sou yon metòd getFullName(). Pou egzanp kontwòl: namespace App\Controller;

use App\Entity\Customer;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
use Symfony\Component\HttpFoundation\JsonResponse;
use Symfony\Component\Routing\Attribute\Route;

class CustomerController extends AbstractController
{
    #[Route('/customer/{id}', methods: ['GET'])]
    public function show(Customer $customer): JsonResponse
    {
        // Serialization automatically includes "fullName" in the JSON output
        return $this->json($customer);
    }
}
 Pwodwi pou: {
  "firstName": "Jane",
  "lastName": "Doe",
  "fullName": "Jane Doe"
}
 Avanse modèl: Value Objects & DTOs Tanpri gade nan yon skenè plis konplèks ki gen rapò ak yon Objè transfè done (DTO) pou yon fòm Symfony oswa API payload. Nou pral itilize dirèkteman sou pwopriyete hooked. validation attributes namespace App\DTO;

use Symfony\Component\Validator\Constraints as Assert;

class RegistrationRequest
{
    #[Assert\NotBlank]
    public string $firstName;

    #[Assert\NotBlank]
    public string $lastName;

    // A 'write-only' property behavior for passwords using a hook
    // We only want to set it, but reading it might return a masked value or be disallowed
    public string $password {
        set(string $value) {
            $this->password = password_hash($value, PASSWORD_BCRYPT);
        }
        get => '***MASKED***'; 
    }
    
    // Combining hooks with asymmetric visibility
    // Publicly readable, but only settable internally or by hydration
    public private(set) \DateTimeImmutable $registeredAt {
        get => $this->registeredAt ?? new \DateTimeImmutable();
    }
}
 : Peye atansyon ak get hook la sou $registeredAt pi wo a. Si pwopriyete a se uninitialized, aksè li atravè $this->registeredAt nan lyen an lakòz infinite recursion. ? tcheke a se yon modèl sekirite si jaden an backing ta ka null. Warning Refactoring yon sèvis Legacy Jwenn yon gade nan yon klas sèvis. Tradisyonèlman, nou ka enjecte dependences ak sèvi ak metòd estanda. Avèk PHP 8.4, nou ka fè konfigirasyon sèvis nou an pi net. : nan ki bezwen yon adrès default "sendè", men nou vle pèmèt chanje l 'temporalman ak validasyon estrikti. Scenario EmailService namespace App\Service;

use Symfony\Component\Mailer\MailerInterface;
use Symfony\Component\Mime\Email;

class EmailService
{
    public function __construct(
        private readonly MailerInterface $mailer,
        // Property Hook to validate configuration immediately
        public string $defaultSender {
            set(string $value) {
                if (!filter_var($value, FILTER_VALIDATE_EMAIL)) {
                    throw new \InvalidArgumentException("Invalid sender email");
                }
                $this->defaultSender = $value;
            }
        }
    ) {}

    public function sendWelcomeEmail(string $recipient): void
    {
        $email = (new Email())
            ->from($this->defaultSender)
            ->to($recipient)
            ->subject('Welcome!')
            ->text('Welcome to our platform.');

        $this->mailer->send($email);
    }
}
 nan : services.yaml services:
    App\Service\EmailService:
        arguments:
            $mailer: '@mailer'
            $defaultSender: '%env(DEFAULT_EMAIL_SENDER)%'
 Si anviwònman an varye gen yon imèl invalide, instantiation sèvis la pral default imedyatman ak yon Eksepsyon klè, olye pou yo default silence pita lè imèl la te voye. . DEFAULT_EMAIL_SENDER This “Fail Fast” approach is enhanced by property hooks Symfony 7.4 konpozan konpatib Symphony Forms depann gwo sou konpozan pou li ak ekri done nan objè ou. PropertyAccessor : nan nan Symfony 7.4 Pwodwi pou Telefòn PHP 8.4 Hooks Good News PropertyAccessor fully supports 
 
 
 Lè fòm la li done yo popile jaden yo, li aktivize get hook la. Lè fòm la soumèt done tounen nan objè a, li aktivize koneksyon an. Transformasyon nan entite a Souvan ou ka retire Form Data Transformers pa deplase logik la nan entite / DTO kouvèti. // Old way: create a CallbackTransformer to handle string-to-array conversion
// New way:

class TagAwareDTO
{
    /** @var string[] */
    private array $tags = [];

    // The form field can be mapped to 'tagString'
    // The underlying data is stored in $tags array
    public string $tagString {
        get => implode(', ', $this->tags);
        set(string $value) {
            $this->tags = array_map('trim', explode(',', $value));
        }
    }
    
    public function getTags(): array
    {
        return $this->tags;
    }
}
 Nan fòm ou: $builder->add('tagString', TextType::class, [
    'label' => 'Tags (comma separated)',
]);
 Sa a senplike sensiblman, kenbe logik la nan transformasyon done nan objè domèn nan ki li nan. FormType Konsidere pèfòmans & Pitfalls Malgre ke karakteristik sa yo ekselan, devlopè "Senior" konnen lè yo pa sèvi ak yo. Klonasyon Pitfall Lè ou yon objè, PHP fè yon kopi siperyè. Si ou sèvi ak vizibilite asimetrik, objè a klone kenbe règ yo vizibilite yo menm. clone Epitou, fè atansyon ak Si yon pwopriyete vityèl depann sou yon lòt objè (pwa, ) ak ou klone objè a patnè men pa objè a enteryè , pwopriyete a vityèl la ta ka toujou parèt nan referans itilizatè a fin vye granmoun. Sa a se pwopriyete objè PHP estanda, men hooks ka sove sa a kompleksite. Virtual Properties $this->user->name $user Doktrin nan Proxies Doktrin sèvi ak Proxies (subclasses) pou charj lazy. 
 
 
 Asimetrik Vizibilite: Li travay bon paske Doktrin itilize Refleksyon mete pwopriyete prive. Kouvèti: Si ou defini yon kouvèti sou yon pwopriyete mape, doktrin la pral trigger li lè hydrate entite a si li sèvi ak refleksyon (ki li fè). Sepandan, dwe trè atansyon sou ajoute efè segondè (tankou logging oswa baz baz baz) nan yon kouvèti set nan yon entite doktrin. Lè Doktrin hidrate objè a soti nan DB a, ou pa vle ke efè segondè yo kouri. : Evite efè segondè (logging, apèl API) nan entity hooks. . Best Practice Keep hooks strictly for data validation and transformation Komplikasyon nan kouvri Pa mete 50 liy nan lojik biznis nan yon kouvèti mete. Si logik la se konplèks, delege li nan yon metòd prive oswa, pi bon, yon sèvis. Kouvèti yo ta dwe kout. Bad: public string $status {
    set {
        // 50 lines of code checking permissions, logging to DB, sending emails...
    }
}
 Good: public string $status {
    set {
        $this->validateStatusTransition($value);
        $this->status = $value;
    }
}
 Migrasyon Guide: Soti nan 7.3/8.3 nan 7.4/8.4 Si ou ap amelyore yon baz kòd masiv, pa eseye re-skri tout nan yon sèl fwa. 
 
 
 
 Asimetri Vizibilite. Kòmanse yon regex rechèch oswa sèvi ak Rector (yon fwa mete ajou pou 8.4) ranplase pwopriyete prive + senp getters ak piblik prive(set).Search: prive kalite $prop; ... getProp() {retour $this->prop; }Remplace: piblik prive(set) kalite $prop; Pwopriyete vityèl pou Resous API. Rechèch pou klas ak #[SerializedName(‘virtual_field’)] ak getVirtualField() metòd. Konvèti yo nan pwopriyete vityèl. Validation. Move senp aserte logik ki transfere done (tankou trim() oswa strtolower()) soti nan kontwoleur / listeners nan Property Hooks. Konklisyon ak nou pèmèt nou ekri kòd ki se sansib la pi klè nan istwa a nan lang la. Nou se deplase soti nan verbose, "dumb" estrikti done nan dènye a nan direksyon pou entelijan, objè pwòp tèt ou jesyon. PHP 8.4 Symfony 7.4 Sèvi ak Takeaways 
 
 
 
 
 Sèvi ak Vizibilite Asimetrik (pou piblik prive(sèt)) pou ekspoze done an sekirite san yo pa gout. Sèvi ak Property Hooks pou valizyon limyè, transformasyon, ak pwopriyete vityèl. Symfony Serializer ak Fòm sipòte karakteristik sa yo soti nan bwat la nan 7.4. Tanpri kenbe ankouraje san danje ak vit; evite efè segondè. Se jou yo nan jenerasyon gouters ak setters fini. Byenveni nan èd nan PHP modèn. Èske ekip ou pare yo migre nan Symfony 7.4? Mwen ede òganizasyon modernize aplikasyon PHP legacy ak adopte architectures pèfòmans segondè. : Kòmanse sou LinkedIn [ ] Let’s connect https://www.linkedin.com/in/matthew-mochalkin/ https://www.linkedin.com/in/matthew-mochalkin/

Read My Stories

Odyo sa a pwodui nan lang orijinal istwa a!

Property Hooks nan aksyon: Isit la se kèk egzanp reyèl ou ta dwe gade nan

About Author

KÒMANtè

KANDYE TAGS

ATIK SA A TE PREZANTE NAN

Related Stories

HackerNoon Contributor Nikita Vasilev on Programming, Python, and More

American Equity, by Sam Altman (with comments & highlights)

STOP: In the name of the brand police!

It's Gonna Be May... a New Mobile App Update, Pixelated Avatars, Revamped Story Pages and More

HackerNoon Contributor Nikita Vasilev on Programming, Python, and More

American Equity, by Sam Altman (with comments & highlights)

STOP: In the name of the brand police!

It's Gonna Be May... a New Mobile App Update, Pixelated Avatars, Revamped Story Pages and More

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps