RocketChat / RocketChat/Rocket.Chat

Zip export feature doesn't support multi-line message

Open
#21,445 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

When you choose "Export Message" -> "Export as File", you can get zipped messages.
But all messages are shown as single-line messages even if it's multi-line messages.
This is a fatal readability issue.

Steps to reproduce:

This is an expected reproduction method with open.rocket.chat, but I faced this in my own server wrote in Server Setup Information.

  1. make sure your account has a valid email address
  2. sign in to open.rocket.chat
  3. make a channel or private group
  4. make some message with multiple lines
  5. choose "Export Message" from the option in the channel action bar
  6. choose "Export as File", a term that contains today, "HTML", and click the "Export" button
  7. extract zip from the e-mail
  8. check the HTML
Expected behavior:

all messages are shown, including multi-line messages.

Actual behavior:

They're shown, but each multi-line message was shown as a single-line message (via just ignoring new-line characters).
This makes the archive unreadable if there was a user who makes heavy multi-line messages in the channel/room.

Server Setup Information:
  • Version of Rocket.Chat Server: 3.12.1
  • Operating System: Ubuntu 20.04.2
  • Deployment Method: snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: enabled
  • NodeJS Version: 12.18.4
  • MongoDB Version: 3.6.14
Client Setup Information
  • Desktop App or Browser Version: Desktop App(Electron) 3.1.1
  • Operating System: Windows 10 Pro(arch x64, version 20H2, build 19042.867)
Additional context

Ideally, I think it's better the HTML export feature to support Markdown.

Relevant logs:

none(this problem is about missing-feature, so there is no problematic log)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by tracing the channel action bar's “Export Message” → “Export as File” HTML export flow, then reproduce it with a multi-line message and inspect the extracted HTML. Done means exported messages preserve their line breaks and the existing export behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
full-stack
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.