Skip to content

TGC-842: Fix multilineTextField render issue#188

Merged
alexluckett merged 2 commits intomainfrom
TGC-842-multiline-text-field-render-issue
Sep 4, 2025
Merged

TGC-842: Fix multilineTextField render issue#188
alexluckett merged 2 commits intomainfrom
TGC-842-multiline-text-field-render-issue

Conversation

@davidatdefra
Copy link
Copy Markdown
Contributor

Bug fix

When a multilineTextField component has multiple newlines, the rendering of that output in the summary list is wrong, e.g.

line 1

line 2

line 3

Is displayed as

line 1line2line 3

Ideally the rendered output in the summary list would exactly match the user's input, but marked does not seem to be able to output multiple newlines. Given this limitation and the space constraints of the summary list, I think it's ok to just collapse the newlines into one and render as if the input had been:

line 1
line 2
line 3

Which works fine.

Jira ticket: https://eaflood.atlassian.net/browse/TGC-842

(Description basically the same as above)

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
Copy link
Copy Markdown

sonarqubecloud Bot commented Sep 4, 2025

@alexluckett alexluckett merged commit 2bc7906 into main Sep 4, 2025
10 checks passed
@alexluckett alexluckett deleted the TGC-842-multiline-text-field-render-issue branch September 4, 2025 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants