Use new skip-validation attribute

Author: mnocon

docs/administration/configuration/dynamic_configuration.md

@@ -29,7 +29,7 @@ parameters:
 
 Inside a controller extending the `Ibexa\Core\MVC\Symfony\Controller\Controller` class, in `site_group` SiteAccess, you can use the parameters in the following way (the same applies for `hasParameter()`):
 
-``` php skip-validation
+``` php {skip-validation}
 $configResolver = $this->getConfigResolver();
 
 // ibexa.site_access.config is the default namespace, so no need to specify it

docs/api/graphql/graphql_custom_ft.md

@@ -40,7 +40,7 @@ If not specified, it uses `FieldDefinition`.
 
 Compiler pass example that should be placed in `src/DependencyInjection/Compiler`:
 
-``` php skip-validation
+``` php {skip-validation}
 [[= include_file('code_samples/api/graphql/src/DependencyInjection/Compiler/MyCustomTypeGraphQLCompilerPass.php') =]]
 ```
 

docs/content_management/field_types/field_type_reference/authorfield.md

@@ -41,7 +41,7 @@ The hash format mostly matches the value object. It has the following key `autho
 
 Example
 
-``` php skip-validation
+``` php {skip-validation}
 [
     [
        'id' => 1,

docs/content_management/field_types/field_type_reference/countryfield.md

@@ -12,7 +12,7 @@ This field type represents one or multiple countries.
 
 Example array:
 
-``` php skip-validation
+``` php {skip-validation}
 [
     "JP" => [
         "Name" => "Japan",

docs/multisite/siteaccess/siteaccess_aware_configuration.md

@@ -27,7 +27,7 @@ For more information about the ConfigResolver, namespaces and scopes, see [confi
 The example below assumes you're using an `Acme\ExampleBundle`.
 Remember to register the bundle by adding it to `config/bundles.php`:
 
-``` php skip-validation
+``` php {skip-validation}
 return [
     // ...
     Acme\ExampleBundle\AcmeExampleBundle::class => ['all' => true],

docs/permissions/permission_overview.md

@@ -38,7 +38,7 @@ You can control access to a custom controller by implementing the `performAccess
 
 In the following example the user doesn't have access to the controller unless they have the `section/view` policy:
 
-``` php skip-validation
+``` php {skip-validation}
 use Ibexa\Core\MVC\Symfony\Security\Authorization\Attribute;
 
 public function performAccessCheck(): void
@@ -63,7 +63,7 @@ public function performAccessCheck(): void
 To check if a user has access to an operation, use the `isGranted()` method.
 For example, to check if content can be assigned to a Section:
 
-``` php skip-validation
+``` php {skip-validation}
 $hasAccess = $this->isGranted(
     new Attribute('section', 'assign', ['valueObject' => $contentInfo, 'targets' => [$section]])
 );
@@ -79,6 +79,6 @@ checks the `content/edit` permission for the provided content item at the provid
 
 To block access to a specific action of the controller, add the following to the action's definition:
 
-``` php skip-validation
+``` php {skip-validation}
 $this->denyAccessUnlessGranted(new Attribute('state', 'administrate'));
 ```

docs/personalization/enable_personalization.md

@@ -491,7 +491,7 @@ You can retrieve data returned from the Personalization server and modify it bef
 To modify recommendation data, subscribe to `RecommendationResponseEvent`.
 See [`Event/Subscriber/RecommendationEventSubscriber.php`](https://github.com/ibexa/personalization-client/blob/main/src/lib/Event/Subscriber/RecommendationEventSubscriber.php) for an example:
 
-``` php skip-validation
+``` php {skip-validation}
 public static function getSubscribedEvents(): array
 {
     return [

docs/personalization/integrate_recommendation_service.md

@@ -34,7 +34,7 @@ The following examples show how you can integrate a CLICK event:
 
 PHP:
 
-``` php skip-validation
+``` php {skip-validation}
 $mandator_id = '00000';
 $content_type_id = '1';
 $product_id = '123';
@@ -57,7 +57,7 @@ ycimg.src=url;
 
 A similar tracking image can be placed on a confirmation page that ends the payment process.
 
-``` php skip-validation
+``` php {skip-validation}
 $server = '//event.perso.ibexa.co';
 foreach ($just_bought_products as $product_id) {
    $tracking = $server.'/api/'.$mandator_id.'/buy/'.urlencode(user_id()).$content_type_id.$product_id;
@@ -122,7 +122,7 @@ A response with two recommendations resembles the following object:
 
 You can use the following code to make requests and parse results:
 
-``` php skip-validation
+``` php {skip-validation}
 $mandator_id = '00000';
 $license_key = '67890-1234-5678-90123-4567';
 $server = "https://reco.perso.ibexa.co";

docs/release_notes/ez_platform_v2.4.md

@@ -182,7 +182,7 @@ The biggest benefit of this feature is saving load time on complex landing pages
 
     1\. Register `LexikJWTAuthenticationBundle` bundle in `/app/AppKernel.php`
 
-    ``` php skip-validation
+    ``` php {skip-validation}
      public function registerBundles()
      {
          $bundles = array(

docs/release_notes/ez_platform_v3.0_deprecations.md

@@ -772,7 +772,7 @@ All classes and interfaces from `eZ\Publish\Core\Persistence\Database` and `eZ\P
 The signature of the `\eZ\Publish\Core\Persistence\Legacy\URL\Query\CriterionHandler::handle` contract
 now accepts `\Doctrine\DBAL\Query\QueryBuilder` instead of `\eZ\Publish\Core\Persistence\Database\SelectQuery` and has the following form:
 
-``` php skip-validation
+``` php {skip-validation}
 use \Doctrine\DBAL\Query\QueryBuilder;
 use \eZ\Publish\Core\Persistence\Legacy\URL\Query\CriteriaConverter;
 use \eZ\Publish\API\Repository\Values\URL\Query\Criterion;