Services - 8.9.x - drupal
Introduction to services
A "service" (such as accessing the database, sending email, or translating user interface text) can be defined by a module or Drupal core. Defining a service means giving it a name and designating a default class to provide the service; ideally, there should also be an interface that defines the methods that may be called. Services are collected into the Dependency Injection Container, and can be overridden to use different classes or different instantiation by modules. See the Services and Dependency Injection Container topic for details.
Some services have tags, which are defined in the service definition. Tags are used to define a group of related services, or to specify some aspect of how the service behaves. See the Service Tags topic for more information.
See also
Services and Dependency Injection Container
File
-
core/
core.api.php, line 893
| Title | File name | Summary | All service tags |
|---|---|---|---|
| workspaces.entity_schema_listener | core/ |
Drupal\workspaces\EventSubscriber\EntitySchemaSubscriber | event_subscriber |
| workspaces.manager | core/ |
Drupal\workspaces\WorkspaceManager | service_id_collector |
| workspaces.negotiator.query_parameter | core/ |
Drupal\workspaces\Negotiator\QueryParameterWorkspaceNegotiator | workspace_negotiator |
| workspaces.negotiator.session | core/ |
Drupal\workspaces\Negotiator\SessionWorkspaceNegotiator | workspace_negotiator |
| workspaces.operation_factory | core/ |
Drupal\workspaces\WorkspaceOperationFactory | |
| workspaces.repository | core/ |
Drupal\workspaces\WorkspaceRepository | |
| workspaces.workspace_subscriber | core/ |
Drupal\workspaces\EventSubscriber\WorkspaceRequestSubscriber | event_subscriber |
| workspace_update_test.negotiator.test | core/ |
Drupal\workspace_update_test\Negotiator\TestWorkspaceNegotiator | workspace_negotiator |
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.