Ignore existing samples

Author: mnocon

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -41,7 +41,7 @@ This mechanism can be modified to fit your site needs, so you can decide from wh
 First, create base strategy for returning custom thumbnails from a static file.
 Create `StaticStrategy.php` in `src/Strategy`.
 
-```php
+``` php
 [[= include_code('code_samples/back_office/thumbnails/src/Strategy/StaticThumbnailStrategy.php') =]]
 ```
 
@@ -74,7 +74,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/back_office_tabs/back_office_tabs.md

@@ -18,7 +18,7 @@ A custom tab can extend one of the following classes:
 - [`AbstractControllerBasedTab`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-Tab-AbstractControllerBasedTab.html) - embeds the results of a controller action in the tab
 - [`AbstractRouteBasedTab`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-Tab-AbstractRouteBasedTab.html) - embeds the results of the selected route, passing applicable parameters
 
-``` php
+``` php {skip-validation}
 //...
 [[= include_file('code_samples/back_office/dashboard/article_tab/src/Tab/Dashboard/Everyone/EveryoneArticleTab.php', 16, 18) =]]
     //...

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

@@ -47,7 +47,7 @@ Here, you define a new class for your event based on `Ibexa\Contracts\Calendar\E
 
 Next, create `src/Calendar/Holidays/EventType.php`:
 
-```php hl_lines="20-23"
+``` php hl_lines="20-23"
 [[= include_code('code_samples/back_office/calendar/src/Calendar/Holidays/EventType.php') =]]
 ```
 
@@ -68,7 +68,7 @@ An event source must implement `Ibexa\Contracts\Calendar\EventSource\EventSource
 One such built-in implementation is `InMemoryEventSource`.
 To add an in-memory collection as an event source, create `src/Calendar/Holidays/EventSourceFactory.php`:
 
-```php
+``` php
 [[= include_file('code_samples/back_office/calendar/src/Calendar/Holidays/EventSourceFactory.php', 0, 20) =]]
 [[= include_file('code_samples/back_office/calendar/src/Calendar/Holidays/EventSourceFactory.php', 26, 36) =]]
 
@@ -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/customize_product_tour.md

@@ -40,7 +40,7 @@ ibexa:
 
 Then, create a subscriber that modifies the scenario.
 
-```php hl_lines="32-34 36-38 40-42 44-55"
+``` php hl_lines="32-34 36-38 40-42 44-55"
 [[= include_code('code_samples/back_office/product_tour/src/EventSubscriber/NotificationScenarioSubscriber.php') =]]
 ```
 

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',
@@ -90,7 +90,7 @@ You can send notifications to users which are displayed in the user menu.
 To create a new notification you can use the [`NotificationService::createNotification(CreateStruct $createStruct)` method](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-NotificationService.html#method_createNotification)
 like in the example below:
 
-```php
+``` php
 [[= include_code('code_samples/back_office/notifications/src/EventListener/ContentPublishEventListener.php') =]]
 ```
 
@@ -102,7 +102,7 @@ To display a user notification, write a renderer and tag it as a service.
 
 The example below presents a renderer that uses Twig to render a view:
 
-```php
+``` php
 [[= include_code('code_samples/back_office/notifications/src/Notification/MyRenderer.php') =]]
 ```
 
@@ -126,7 +126,7 @@ To display a list of notifications, expand the above renderer.
 
 The example below presents a modified renderer that uses Twig to render a list view:
 
-```php
+``` php
 [[= include_code('code_samples/back_office/notifications/src/Notification/ListRenderer.php') =]]
 ```
 

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;