Disabled validation for existing inline PHP snippets

Author: mnocon

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -75,7 +75,7 @@ It enables you to add a thumbnail URL in the text field.
 
 Add `FieldValueUrl.php` in `src/Thumbnails`.
 
-```php
+```php {skip-validation}
 <?php
 
 declare(strict_types=1);

docs/administration/back_office/back_office_elements/formatting_date_and_time.md

@@ -19,7 +19,7 @@ You can format date and time by using the following services:
 
 To use them, create an `src/Service/MyService.php` file containing:
 
-``` php
+``` php {skip-validation}
 <?php
 
 namespace App\Service;

docs/administration/back_office/back_office_menus/back_office_menus.md

@@ -85,7 +85,7 @@ The following method adds a new menu section under **Content**, and under it, a
 
 You can also pass parameters to templates used to render menu items with `template_parameters`:
 
-``` php
+``` php {skip-validation}
 $menu->addChild(
     'all_content_list',
     [
@@ -105,7 +105,7 @@ You can then use the variable `custom_parameter` in `templates/themes/admin/list
 
 To have translatable labels, use `translation.key` from the `messages` domain:
 
-``` php
+``` php {skip-validation}
 $menu->addChild(
     'all_content_list',
     [

docs/administration/back_office/browser/browser.md

@@ -146,7 +146,7 @@ If an event listener catches additional parameters passed with context, it uses
 
 In the example below, the `johndoe` parameter enables the user to choose multiple items from a **Browser window** by changing `multiple: false` from `my_custom_udw` configuration to `multiple: true`.
 
-```php hl_lines="29 30 31"
+```php {skip-validation} hl_lines="29 30 31"
 class JohnDoeCanSelectMore implements EventSubscriberInterface
 {
     private const CONFIGURATION_NAME = 'my_custom_udw';

docs/administration/back_office/customize_calendar.md

@@ -80,7 +80,7 @@ To add an in-memory collection as an event source, create `src/Calendar/Holidays
 
     For example:
 
-    ``` php
+    ``` php {skip-validation}
     $collection = new EventCollection([
         $this->createEvent("Event 1", new DateTime("2024-01-01")),
         $this->createEvent("Event 2", new DateTime("2024-01-02")),

docs/administration/back_office/notifications.md

@@ -25,7 +25,7 @@ There are four types of notifications: `info`, `success`, `warning` and `error`.
 
 To send a notification from PHP, inject the `TranslatableNotificationHandlerInterface` into your class.
 
-``` php
+``` php {skip-validation}
 $this->notificationHandler->info(
     /** @Desc("Notification text") */
     'example.notification.text',

docs/administration/configuration/configuration.md

@@ -72,7 +72,7 @@ parameters:
         an_array: [apple, banana, pear]
 ```
 
-``` php
+``` php {skip-validation}
 // Usage inside a controller
 $myParameter = $this->container->getParameter( 'myapp.parameter.name' );
 ```

docs/administration/configuration/dynamic_configuration.md

@@ -29,7 +29,7 @@ parameters:
 
 Inside a controller, in `site_group` SiteAccess, you can use the parameters in the following way (the same applies for `hasParameter()`):
 
-``` php
+``` php {skip-validation}
 $configResolver = $this->getConfigResolver();
  
 // ibexa.site_access.config is the default namespace, so no need to specify it
@@ -77,7 +77,7 @@ For more information about dependency injection, see [Service container](php_api
     Don't store the retrieved config value unless you know what you're doing.
     SiteAccess can change during code execution, which means you might work on the wrong value.
 
-``` php
+``` php {skip-validation}
 namespace App;
 
 use Ibexa\Contracts\Core\SiteAccess\ConfigResolverInterface;

docs/administration/configuration/repository_configuration.md

@@ -303,7 +303,7 @@ This enables you to use different settings for different repositories.
 
 To do this, create a parser that implements `Ibexa\Bundle\Core\DependencyInjection\Configuration\RepositoryConfigParserInterface`:
 
-``` php
+``` php {skip-validation}
 use Ibexa\Bundle\Core\DependencyInjection\Configuration\RepositoryConfigParserInterface;
 use Symfony\Component\Config\Definition\Builder\NodeBuilder;
 
@@ -326,7 +326,7 @@ final class CustomRepositoryConfigParser implements RepositoryConfigParserInterf
 
 You need to register this configuration extension in the following way:
 
-``` php
+``` php {skip-validation}
 final class AcmeFeatureBundle extends Bundle
 {
     public function build(ContainerBuilder $container): void
@@ -342,6 +342,6 @@ final class AcmeFeatureBundle extends Bundle
 
 To access the configuration settings, use the `Ibexa\Bundle\Core\ApiLoader\RepositoryConfigurationProvider::getRepositoryConfig` method:
 
-``` php
+``` php {skip-validation}
 $acmeConfig = $repositoryConfigProvider->getRepositoryConfig()['acme'];
 ```

docs/ai_actions/configure_ai_actions.md

@@ -91,7 +91,7 @@ composer require ibexa/connector-gemini
 
 Then, if not using Symfony Flex, enable the bundle in `config/bundles.php`:
 
-``` php
+``` php {skip-validation}
     Ibexa\Bundle\ConnectorGemini\IbexaConnectorGeminiBundle::class => ['all' => true],
 ```