/** * @covers ::delete * @covers ::doDelete */ public function testDeleteNothing() { $this->moduleHandler->expects($this->never())->method($this->anything()); $this->configFactory->expects($this->never())->method('get'); $this->cacheTagsInvalidator->expects($this->never())->method('invalidateTags'); $this->entityStorage->delete(array()); }
/** * {@inheritdoc} */ public function delete(array $entities) { $return = parent::delete($entities); return $return; }
/** * {@inheritdoc} */ public function delete(array $entities) { $return = parent::delete($entities); // Update the state of registered events. // @todo Should we trigger a container rebuild here as well? Might be a bit // expensive on every delete? $this->stateService->set('rules.registered_events', $this->getRegisteredEvents()); return $return; }
/** * {@inheritdoc} */ public function delete(array $entities) { // After deleting a set of reaction rules, sometimes we may need to rebuild // the container, to clean it up, so that the generic subscriber is not // registered in the container for the rule events which we do not use // anymore. So we do that if there is any change in the registered events, // after the reaction rules are deleted. $events_before = $this->getRegisteredEvents(); $return = parent::delete($entities); $events_after = $this->getRegisteredEvents(); // Update the state of registered events and rebuild the container. if ($events_before != $events_after) { $this->stateService->set('rules.registered_events', $events_after); $this->drupalKernel->rebuildContainer(); } return $return; }