ProblemDetailsProcessor Configurations Table View¶
TL;DR — Use this generated field table to check property paths, types, required status, defaults, and descriptions.
When to use¶
Use this page when you need the exact field path or value type for a hook configuration before editing YAML.
YAML configuration¶
The table below mirrors the schema used by the YAML scaffold page. Nested rows use dotted paths and [] for list items.
| Property Path | Type | Required | Default | Description |
|---|---|---|---|---|
ProcessorConfiguration | object or string | ✖ | ||
ProcessorConfiguration.ContentType | string | ✔ | Response Content-Type header | |
ProcessorConfiguration.StatusCode | integer or string | ✔ | Response Status Code | |
ProcessorConfiguration.Title | string | ✔ | Problem details title | |
ProcessorConfiguration.Type | string | ✔ | Problem details type | |
ProcessorConfiguration.Detail | string or null | ✖ | Problem details detail | |
ProcessorConfiguration.Extensions | object or string or null | ✖ | Additional problem details extension fields | |
ProcessorConfiguration.Instance | string or null | ✖ | Explicit problem details instance | |
ProcessorConfiguration.ResponseHeaders | object or string or null | ✖ | Additional response headers | |
ProcessorConfiguration.UseRequestUriAsInstance | string or true/false | ✖ | Use the request URI as the problem details instance when no explicit instance is configured |
Edge cases¶
- Empty default cells mean the schema does not define a default value for that field.
- Required status applies to the immediate parent object shown by the property path.