From b909ecefd2958eb8bcbea5eb8d510fa07bae1df3 Mon Sep 17 00:00:00 2001 From: Antoine Makdessi Date: Tue, 28 Dec 2021 16:48:03 +0100 Subject: [PATCH 1/2] Update best_practices.rst --- best_practices.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/best_practices.rst b/best_practices.rst index f18c756c2fc..537bdc4637f 100644 --- a/best_practices.rst +++ b/best_practices.rst @@ -378,7 +378,8 @@ Use Voters to Implement Fine-grained Security Restrictions If your security logic is complex, you should create custom :doc:`security voters ` instead of defining long expressions -inside the ``@Security`` annotation. +inside the ``Security`` attribute +(or annotation if your PHP version doesn't support attributes yet). Web Assets ---------- From da844ef4c7625cd48e0b5826ec3a286a29d32d26 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Wed, 29 Dec 2021 15:38:59 +0100 Subject: [PATCH 2/2] Minor tweak --- best_practices.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/best_practices.rst b/best_practices.rst index 537bdc4637f..ccdc8d17852 100644 --- a/best_practices.rst +++ b/best_practices.rst @@ -378,8 +378,8 @@ Use Voters to Implement Fine-grained Security Restrictions If your security logic is complex, you should create custom :doc:`security voters ` instead of defining long expressions -inside the ``Security`` attribute -(or annotation if your PHP version doesn't support attributes yet). +inside the ``#[Security]`` attribute (or in the ``@Security`` annotation if your +PHP version doesn't support attributes yet). Web Assets ----------