Skip to content

Remove markdown links note on /create#4465

Open
leonardthethird wants to merge 1 commit intomainfrom
claude/issue-4462-remove-markdown-links-note-on
Open

Remove markdown links note on /create#4465
leonardthethird wants to merge 1 commit intomainfrom
claude/issue-4462-remove-markdown-links-note-on

Conversation

@leonardthethird
Copy link
Contributor

@leonardthethird leonardthethird commented Mar 10, 2026

Closes #4462

Remove the obsolete markdown syntax reference from the background info explanation on the question creation page. The WYSIWYG editor makes this note unnecessary.

Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Streamlined background information guidance text across all supported languages by removing markdown syntax examples. Users now see simplified, clearer instructions focused on adding relevant and helpful resources.

The WYSIWYG editor makes the markdown syntax note obsolete. Remove
the markdown format reference while keeping the instruction to add
links to relevant resources.

Closes #4462

Co-authored-by: leonardthethird <leonardthethird@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 10, 2026

📝 Walkthrough

Walkthrough

This PR removes markdown syntax guidance from the backgroundInfoExplanation message across six language translation files and simplifies the corresponding React components to render this message as plain text instead of rich content, eliminating the rich text composition pattern.

Changes

Cohort / File(s) Summary
Translation Files
front_end/messages/cs.json, front_end/messages/en.json, front_end/messages/es.json, front_end/messages/pt.json, front_end/messages/zh-TW.json, front_end/messages/zh.json
Removed markdown syntax guidance and markdown link examples from backgroundInfoExplanation field. Simplified text now instructs to add links to relevant resources without referencing markdown format.
Component Files
front_end/src/app/(main)/questions/components/group_form.tsx, front_end/src/app/(main)/questions/components/question_form.tsx
Replaced rich text rendering (Link and MarkdownText composition via t.rich) with plain string translation (t("backgroundInfoExplanation")). Removed unused next/link import.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • elisescu
  • hlbmtc

Poem

🐰 Markdown syntax fades away,
Plain and simple saves the day,
WYSIWYG leads the way,
Translation strings in fresh display! ✨

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately describes the main change: removing markdown links guidance from the question creation page.
Linked Issues check ✅ Passed All coding changes align with issue #4462 requirements: markdown format references removed from all language message files and corresponding React components.
Out of Scope Changes check ✅ Passed All changes are directly scoped to removing markdown link syntax guidance; no unrelated modifications are present.

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

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/issue-4462-remove-markdown-links-note-on

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@front_end/messages/es.json`:
- Line 697: The Spanish string for the translation key
"backgroundInfoExplanation" uses awkward phrasing "Los enlaces deben agregarse a
recursos relevantes y útiles"; update that value to a clearer imperative such as
"Agrega enlaces a recursos relevantes y útiles" (or "Incluye enlaces a recursos
relevantes y útiles") while keeping the rest of the message unchanged so the key
"backgroundInfoExplanation" reads: "Proporciona información de fondo para tu
pregunta en un tono objetivo y sin sesgos. Agrega enlaces a recursos relevantes
y útiles."

In `@front_end/messages/zh-TW.json`:
- Line 845: The zh-TW string for the key "backgroundInfoExplanation" mixes
Simplified Chinese terms; update its value to use Traditional Chinese wording
(e.g., replace "信息" with "資訊" and use "連結" instead of the Simplified form) so
the entry reads naturally in the Traditional Chinese catalog — locate the
"backgroundInfoExplanation" entry and change its text accordingly (for example:
"以事實和不偏不倚的語氣提供問題的背景資訊。連結應添加至相關和有用的資源。").

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bd0c0f04-d815-450d-a019-cf8bd6033434

📥 Commits

Reviewing files that changed from the base of the PR and between 97144b1 and 58e6d4f.

📒 Files selected for processing (8)
  • front_end/messages/cs.json
  • front_end/messages/en.json
  • front_end/messages/es.json
  • front_end/messages/pt.json
  • front_end/messages/zh-TW.json
  • front_end/messages/zh.json
  • front_end/src/app/(main)/questions/components/group_form.tsx
  • front_end/src/app/(main)/questions/components/question_form.tsx

"shortTitleExplanation": "Debe ser una versión más corta del Título Largo, utilizada donde hay menos espacio para mostrar un título. Debe terminar con un signo de interrogación. Ejemplos: \"¿Ganador del contrato de trajes espaciales de la NASA 2022?\" o \"¿PIB de la UE de 2025 a 2035?\"",
"backgroundInformation": "Información de Fondo",
"backgroundInfoExplanation": "Proporciona información de fondo para tu pregunta en un tono objetivo y sin sesgos. Los enlaces deben agregarse a recursos relevantes y útiles utilizando la <link>sintaxis markdown</link>: <markdown>[Título del Enlace](https://link-url.com)</markdown>.",
"backgroundInfoExplanation": "Proporciona información de fondo para tu pregunta en un tono objetivo y sin sesgos. Los enlaces deben agregarse a recursos relevantes y útiles.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Tighten the Spanish wording for the link instruction.

Los enlaces deben agregarse a recursos relevantes y útiles reads awkwardly in Spanish; it sounds like links are being added to the resources. Something like Agrega enlaces a recursos relevantes y útiles or Incluye enlaces a recursos relevantes y útiles is clearer.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@front_end/messages/es.json` at line 697, The Spanish string for the
translation key "backgroundInfoExplanation" uses awkward phrasing "Los enlaces
deben agregarse a recursos relevantes y útiles"; update that value to a clearer
imperative such as "Agrega enlaces a recursos relevantes y útiles" (or "Incluye
enlaces a recursos relevantes y útiles") while keeping the rest of the message
unchanged so the key "backgroundInfoExplanation" reads: "Proporciona información
de fondo para tu pregunta en un tono objetivo y sin sesgos. Agrega enlaces a
recursos relevantes y útiles."

"shortTitleExplanation": "此處應為長標題的較短版本,用於空間有限的標題展示。應以問號結尾。例子:“NASA 2022太空衣合約得獎者?”或“2025至2035的歐盟GDP?”",
"backgroundInformation": "背景信息",
"backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景信息。鏈接應使用<link>Markdown語法</link>添加至相關和有用的資源:<markdown>[鏈接標題](https://link-url.com)</markdown>。",
"backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景信息。鏈接應添加至相關和有用的資源。",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Use Traditional Chinese wording in the zh-TW locale.

Line 845 mixes in Simplified terms (信息, 鏈接), which will read oddly in the Traditional Chinese catalog.

Suggested fix
-  "backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景信息。鏈接應添加至相關和有用的資源。",
+  "backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景資訊。連結應添加至相關和有用的資源。",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景信息。鏈接應添加至相關和有用的資源",
"backgroundInfoExplanation": "以事實和不偏不倚的語氣提供問題的背景資訊。連結應添加至相關和有用的資源",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@front_end/messages/zh-TW.json` at line 845, The zh-TW string for the key
"backgroundInfoExplanation" mixes Simplified Chinese terms; update its value to
use Traditional Chinese wording (e.g., replace "信息" with "資訊" and use "連結"
instead of the Simplified form) so the entry reads naturally in the Traditional
Chinese catalog — locate the "backgroundInfoExplanation" entry and change its
text accordingly (for example: "以事實和不偏不倚的語氣提供問題的背景資訊。連結應添加至相關和有用的資源。").

@github-actions
Copy link
Contributor

🚀 Preview Environment

Your preview environment is ready!

Resource Details
🌐 Preview URL https://metaculus-pr-4465-claude-issue-4462-remove-markd-preview.mtcl.cc
📦 Docker Image ghcr.io/metaculus/metaculus:claude-issue-4462-remove-markdown-links-note-on-58e6d4f
🗄️ PostgreSQL NeonDB branch preview/pr-4465-claude-issue-4462-remove-markd
Redis Fly Redis mtc-redis-pr-4465-claude-issue-4462-remove-markd

Details

  • Commit: d6a1c6cda450b2207768370f2af56a28043b6c8c
  • Branch: claude/issue-4462-remove-markdown-links-note-on
  • Fly App: metaculus-pr-4465-claude-issue-4462-remove-markd

ℹ️ Preview Environment Info

Isolation:

  • PostgreSQL and Redis are fully isolated from production
  • Each PR gets its own database branch and Redis instance
  • Changes pushed to this PR will trigger a new deployment

Limitations:

  • Background workers and cron jobs are not deployed in preview environments
  • If you need to test background jobs, use Heroku staging environments

Cleanup:

  • This preview will be automatically destroyed when the PR is closed

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.

Remove markdown links note on /create

3 participants