SETTINGS
SETTINGS = 'strata.settings'
The configuration object every settings form edits.
Where spans and metrics are sent.
An empty endpoint switches the whole subsystem off, including the tracer, so a site with no collector pays nothing for the instrumentation rather than buffering spans nobody reads.
Headers are entered as one Name: value per line and stored as a mapping. They are the only place
an API key belongs, so the field is a plain textarea and its contents are stored in configuration
like any other setting - a site that exports its configuration will export this too, which is
worth knowing before an authorization token goes in it.
$engine : ?\Drupal\strata\Engine
The engine, reset after a save.
create(\Symfony\Component\DependencyInjection\ContainerInterface $container) : static
{@inheritdoc}
The engine is asked for, never required. composer.json PSR-4 maps Drupal\strata\ onto
src/, so every class here loads off composer's autoloader whether or not the module is in
core.extension, while strata.services.yml reaches the container only when it is. A router
table still holding this route after the module left - a failed install, a composer remove
with no uninstall - therefore resolves the class, calls this, and answered 500 with
ServiceNotFoundException until 1.0.3. The property is nullable and every use of it is
null-safe, so asking is the whole fix.
| \Symfony\Component\DependencyInjection\ContainerInterface | $container |
coerce(mixed $value, string $type) : mixed
Coerces a submitted value to the type the config schema declares.
A form always submits strings, and configuration is schema-validated on save, so an integer
setting handed the string "15" fails validation on a site running strictConfigSchema.
| mixed | $value | The submitted value. |
| string | $type | One of "string", "int", "float" or "bool". |
The coerced value.