hotfix/BA-3024-fe-markdown-improvement

[davidbermudez-tsl]

Original Story:
Acceptance Criteria
Context
Whenever we send a message that uses a markdown format, it is not displayed as intended.

Business Rules

Markdown elements behave as expected in standard messaging and documentation applications.

Formatting remains consistent across different devices and screen sizes.

No display issues such as incorrect colors, spacing, or layout misalignment.

Inline code should:

Display in a standard monospaced font.

Have a subtle background color (not yellow or unintended colors).

Ordered lists and unordered lists should:

Display correct numbering or bullet points.

Be properly indented.

Maintain consistent spacing between list items.

Quote blocks should:

Expand properly within the chat bubble.

Be visually distinct and not squeezed.

Code blocks should

Render within a properly formatted container.

Avoid text overlap or breaking issues.

Markdown input box should:

Follow the correct borders and layout of the message input box.

Markdown elements behave as expected in standard messaging and documentation applications.

Formatting remains consistent across different devices and screen sizes.

No display issues such as incorrect colors, spacing, or layout misalignment.

Current behavior

Expected behavior

Code Snippet

Notes

Try with the new editor: https://github.com/mdx-editor/editor

If it doesn't work we can try to use the preview one: https://github.com/uiwjs/react-markdown-preview

To start we need to do a rebase

It's important to check the message preview below a group or the person name

Approvd
https://app.approvd.io/silverlogic/BA/stories/43064

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2d29acb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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

[anicioalexandre]

could we extract this component and place it at packages/design-system/components/web/inputs?
we could even consider creating a packages/design-system/components/web/markdowns folder and move it all there

[lokmanliton]

1. Numbered list is not working, after sending the message I don't see number and indentation,
2. For bullet point - I see it is working at message box, not in text-box,
3. After sending message, message text-box doesn't become empty, texts are still there,
4. bullet point goes inside the coding block,

https://www.loom.com/share/99a7c6d35d774915b05055d2b8062976