[nayij]

Proposed change

A multiline answer with lines starting with > (e.g. > first / > / > second) caused a 500 on Check your answers. escapeMarkdown didn't escape >, so the answer was read as a quote, and marked threw on the blank line inside it (Token with "space" type was not found). This escapes > so the answer shows as typed, on the summary page and in GOV.UK Notify emails.

Jira ticket: DF-1535

Type of change

• Bug fix
• New feature
• Breaking change
• Misc. (documentation, build updates, etc)

Checklist

• You have executed this code locally and it performs as expected.
• You have added tests to verify your code works.
• You have added code comments and JSDoc, where appropriate.
• There is no commented-out code.
• You have added developer docs in README.md and docs/* (where appropriate, e.g. new features).
• The tests are passing (npm run test).
• The linting checks are passing (npm run lint).
• The code has been formatted (npm run format).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Scullyon]

LGTM. Might be worthwhile adding in an explicit test for escapeMarkdown that's in the file src/server/plugins/engine/components/helpers/index.ts