In the request validation examples, a validator who approves with a comment writes it to the validation variable (routing on validation.result proves the write), but the operator viewing the submission at the process step sees the OLD "request changes" note instead. Two gaps compound:
- WebformInteraction only surfaces feedback_variable as an edit-form prefill query parameter; view mode has no way to render the variable's current comment, and the process steps in both example workflows configure no feedback_variable anyway.
- The prefill writes the reviewer note into a real submission element (feedback, prepopulate plus readonly on request_form_link), so each "request changes" note is frozen into the submission at resubmit time and later shown to everyone as if current.
Fix: teach WebformInteraction view mode to render the feedback_variable's current comment as a labelled "Reviewer note" item above the submission view; set feedback_variable: validation on the process step in request_validation and request_validation_link; retitle the baked-in element so the frozen copy is honest (for example "Reviewer feedback at last revision"). Add a kernel test covering approve-with-comment after a changes round.
Issue fork orchestra-3608397
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
mably commentedComment #4
mably commentedMR !285 reworks this generically rather than patching the prefill (nothing released, so the old mechanism is replaced outright).
Coverage: a new ContextMessages kernel test (dotted paths, severity fallback, config-shaped entry sanitizing, branch-scoped resolution), and RequestValidationTest drives the reported regression end to end over HTTP in both doorways: the poster sees the changes note on every wizard page and on reload until the resubmit, the confirmation page does not repeat it, and the processor sees the current approval comment instead of the stale note. Also validated manually on a live site.
The issue title was updated to describe the rework, since it becomes the commit message.
Comment #6
mably commented