public static DynamicPageCacheSubscriber::getSubscribedEvents() Returns an array of event names this subscriber wants to listen to. The array keys are event names and the value can be: The method name to call (priority defaults to 0) An array composed of the method name to call and the priority An array of arrays composed of the method names to call and respective priorities, or 0 if unset For instance: array('eventName' => 'methodName') array('eventName' => array('methodName', $prior

A response policy rule determining the cacheability of the response. Type: \Drupal\Core\PageCache\ResponsePolicyInterface File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 54 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $responsePolicy;

Internal cache of request policy results. Type: \SplObjectStorage File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 97 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $requestPolicyResults;

A request policy rule determining the cacheability of a response. Type: \Drupal\Core\PageCache\RequestPolicyInterface File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 47 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $requestPolicy;

The renderer configuration array. Type: array File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 68 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $rendererConfig;

The render cache. Type: \Drupal\Core\Render\RenderCacheInterface File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 61 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $renderCache;

Dynamic Page Cache's redirect render array. Type: array File core/modules/dynamic_page_cache/src/EventSubscriber/DynamicPageCacheSubscriber.php, line 75 Class DynamicPageCacheSubscriber Returns cached responses as early and avoiding as much work as possible. Namespace Drupal\dynamic_page_cache\EventSubscriber Code protected $dynamicPageCacheRedirectRenderArray = [ '#cache' => [ 'keys' => ['response'], 'contexts' => [ 'route', // Some routes' controllers r

Returns cached responses as early and avoiding as much work as possible. Dynamic Page Cache is able to cache so much because it utilizes cache contexts: the cache contexts that are present capture the variations of every component of the page. That, combined with the fact that cacheability metadata is bubbled, means that the cache contexts at the page level represent the complete set of contexts that the page varies by. The reason Dynamic Page Cache is implemented as two event subscribers (a la

public DynamicallyFieldableEntityStorageSchemaInterface::requiresFieldStorageSchemaChanges(FieldStorageDefinitionInterface $storage_definition, FieldStorageDefinitionInterface $original) Checks if the changes to the storage definition requires schema changes. Parameters \Drupal\Core\Field\FieldStorageDefinitionInterface $storage_definition: The updated field storage definition. \Drupal\Core\Field\FieldStorageDefinitionInterface $original: The original field storage definition. Return value bo

public DynamicallyFieldableEntityStorageSchemaInterface::requiresFieldDataMigration(FieldStorageDefinitionInterface $storage_definition, FieldStorageDefinitionInterface $original) Checks if existing data would be lost if the schema changes were applied. If there are no schema changes needed, then no data needs to be migrated, but it is not the responsibility of this function to recheck what requiresFieldStorageSchemaChanges() checks. Rather, the meaning of what this function returns when requir