public function Server::preSave in GraphQL 8.4

Acts on an entity before the presave hook is invoked.

Used before the entity is saved and before invoking the presave hook. Note that in case of translatable content entities this callback is only fired on their current translation. It is up to the developer to iterate over all translations if needed. This is different from its counterpart in the Field API, FieldItemListInterface::preSave(), which is fired on all field translations automatically. @todo Adjust existing implementations and the documentation according to https://www.drupal.org/node/2577609 to have a consistent API.

Parameters

\Drupal\Core\Entity\EntityStorageInterface $storage: The entity storage object.

Throws

\Exception When there is a problem that should prevent saving the entity.

Overrides ConfigEntityBase::preSave

File

src/Entity/Server.php, line 508

Class

Server: The main GraphQL configuration and request entry point.

Namespace

Drupal\graphql\Entity

Code

public function preSave(EntityStorageInterface $storage) : void {

  // Write all the persisted queries configuration.
  $persistedQueryInstances = $this
    ->getPersistedQueryInstances();

  // Reset settings array after getting instances as it might be used when
  // obtaining them. This would break a config import containing persisted
  // queries settings as it would end up empty.
  $this->persisted_queries_settings = [];
  if (!empty($persistedQueryInstances)) {
    foreach ($persistedQueryInstances as $plugin_id => $plugin) {
      $this->persisted_queries_settings[$plugin_id] = $plugin
        ->getConfiguration();
    }
  }
  parent::preSave($storage);
}

You are here