bugfix/BA-3301-fe-multiline-posts-is-showing-in-single-line

[davidbermudez-tsl]

Wasn't able to reproduce bug, but added Markdown editor as @nossila recommended.

Summary by CodeRabbit

• New Features
  • Post content editor now features a Markdown editor, enabling users to format text with improved editing capabilities.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 51b3811

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]

📝 Walkthrough

Walkthrough

PostForm replaces its plain-text TextField with MarkdownEditorField for the content input. The import statement is updated, and the field configuration switches to use the new markdown editor component with the same placeholder text.

Changes

Content Editor Field

Layer / File(s)	Summary
Markdown editor field integration packages/components/modules/content-feed/web/PostForm/index.tsx	Import MarkdownEditorField and replace the multiline TextField with MarkdownEditorField for the content form field, maintaining the placeholder and form control binding.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit sees a post form so plain,
Where text fields lacked markdown's refrain,
With a hop and a bound, a new field's found,
MarkdownEditorField saves the day,
Rich formatting comes to play! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the bug being fixed (multiline posts showing in single line) and directly relates to the main change (replacing TextField with MarkdownEditorField).
Description check	✅ Passed	The description is minimal but provides meaningful context about the fix implementation and acknowledges the recommended approach by a colleague.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hotfix/BA-3301-fe-multiline-posts-is-showing-in-single-line

---

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

[coderabbitai]

🧹 Nitpick comments (1)

packages/components/modules/content-feed/web/PostForm/index.tsx (1)

45-49: 📐 Maintainability & Code Quality | ⚡ Quick win

Consider explicit height configuration for consistent UX.

The previous TextField had rows={4} to control height. Consider adding minHeight or similar sizing props to MarkdownEditorField to maintain visual consistency with the original design.

💡 Example configuration

 <MarkdownEditorField
   name="content"
   placeholder="What is on your mind?"
   control={form.control}
+  minHeight={100}
 />

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/components/modules/content-feed/web/PostForm/index.tsx` around lines
45 - 49, The MarkdownEditorField in PostForm currently lacks an explicit height
causing inconsistent UI compared to the previous TextField with rows={4}; update
the MarkdownEditorField usage (name="content", control={form.control}) to
include a sizing prop or style (e.g., minHeight, height, or a rows-equivalent)
so the editor defaults to the original visual height (approx. 4 text rows) and
preserves layout consistency across devices.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@packages/components/modules/content-feed/web/PostForm/index.tsx`:
- Around line 45-49: The MarkdownEditorField in PostForm currently lacks an
explicit height causing inconsistent UI compared to the previous TextField with
rows={4}; update the MarkdownEditorField usage (name="content",
control={form.control}) to include a sizing prop or style (e.g., minHeight,
height, or a rows-equivalent) so the editor defaults to the original visual
height (approx. 4 text rows) and preserves layout consistency across devices.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a33a0e4f-58ac-4681-bf6b-de9a655afbf9

📥 Commits

Reviewing files that changed from the base of the PR and between c6ae399 and 51b3811.

📒 Files selected for processing (1)

• packages/components/modules/content-feed/web/PostForm/index.tsx