Description
In the push detail view, when a validation step fails (e.g. diff scan), the ▼ details expand panel shows only s.content — which for diff scan is just the ref name (ref: refs/heads/...). The actual error message stored in s.errorMessage / s.blockedMessage (e.g. blocked pattern: ... in file.json) is never shown in the expanded view.
The inline row summary does show the message, but it is CSS-truncated (truncate class) so long messages are cut off and can only be read by text-selecting and copy-pasting.
Steps to reproduce
- Push to a branch that triggers a diff scan failure
- Open the push detail page in the dashboard
- Click ▼ details on the failing diff scan step
- Observe: expanded block shows only
ref: refs/heads/<branch>, not the blocked pattern or file path
Expected
Expanded block shows the full errorMessage / blockedMessage (e.g. blocked pattern: X in file Y), with content shown below it as supplementary context if present.
Notes
Discovered while testing the provider field-name fix (PR #243), which includes a fix for this.
Description
In the push detail view, when a validation step fails (e.g. diff scan), the ▼ details expand panel shows only
s.content— which for diff scan is just the ref name (ref: refs/heads/...). The actual error message stored ins.errorMessage/s.blockedMessage(e.g.blocked pattern: ... in file.json) is never shown in the expanded view.The inline row summary does show the message, but it is CSS-truncated (
truncateclass) so long messages are cut off and can only be read by text-selecting and copy-pasting.Steps to reproduce
ref: refs/heads/<branch>, not the blocked pattern or file pathExpected
Expanded block shows the full
errorMessage/blockedMessage(e.g.blocked pattern: X in file Y), withcontentshown below it as supplementary context if present.Notes
Discovered while testing the provider field-name fix (PR #243), which includes a fix for this.