Add new-line support to chat messages #82

New Issue
Open
opened 2026-07-14 13:00:20 +02:00 by retoor · 9 comments
retoor commented 2026-07-14 13:00:20 +02:00
Owner
Copy Link

Summary

Chat messages currently do not support new-lines or line-breaks. Users cannot insert line breaks when composing messages.

Steps to Reproduce

Not provided.

Expected Behaviour

Chat should allow users to insert new-lines or line-breaks in messages.

Actual Behaviour

New-lines or line-breaks are not supported in chat messages.

Environment

Not provided.

Reported by Wojtek322 via DevPlace.

## Summary Chat messages currently do not support new-lines or line-breaks. Users cannot insert line breaks when composing messages. ## Steps to Reproduce Not provided. ## Expected Behaviour Chat should allow users to insert new-lines or line-breaks in messages. ## Actual Behaviour New-lines or line-breaks are not supported in chat messages. ## Environment Not provided. --- *Reported by **Wojtek322** via DevPlace.*
plan-ticket-82.md
3.8 KiB
plan-ticket-82.md
3.7 KiB
typosaurus commented 2026-07-19 23:56:43 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-19 23:56:55 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-19 23:59:49 +02:00
Collaborator
Copy Link

I compared the ticket's claim against the current source code, tests, and external documentation. The investigation shows that newlines are already fully supported across input, submission, storage, rendering, and display. The reported problem does not exist in the current codebase.

This mismatch suggests the ticket may be based on an outdated or inaccurate observation. To resolve this, could you confirm whether the ticket is still accurate or should be closed?

I compared the ticket's claim against the current source code, tests, and external documentation. The investigation shows that newlines are already fully supported across input, submission, storage, rendering, and display. The reported problem does not exist in the current codebase. This mismatch suggests the ticket may be based on an outdated or inaccurate observation. To resolve this, could you confirm whether the ticket is still accurate or should be closed?
typosaurus commented 2026-07-23 01:15:44 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-23 01:16:24 +02:00
Collaborator
Copy Link

I need input to continue.

What I tried: Retried this step 3 times.
What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket.

The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.

I need input to continue. What I tried: Retried this step 3 times. What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket. The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.
typosaurus commented 2026-07-23 03:01:05 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-23 03:01:25 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-23 04:03:06 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-23 04:06:03 +02:00
Collaborator
Copy Link

After reviewing the current source code, test coverage, and external documentation, the system fully supports newlines in chat messages across input, storage, rendering, and display layers. The ticket’s claim that this feature is missing does not match the observed implementation.

Could you confirm whether this description still reflects the intended scope, or should the ticket be closed as a mismatch?

After reviewing the current source code, test coverage, and external documentation, the system fully supports newlines in chat messages across input, storage, rendering, and display layers. The ticket’s claim that this feature is missing does not match the observed implementation. Could you confirm whether this description still reflects the intended scope, or should the ticket be closed as a mismatch?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#82
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?