fix(bot): collect /vaga descricao via modal, not a single-line option

[LucasSantana-Dev]

Problem

/vaga's published requirements list was coming out as one run-on paragraph instead of a bullet list, e.g.:

• Requisito A. - Requisito B. - Requisito C.

Root cause

descricao was a plain Discord slash-command string option — a single-line input. Discord doesn't support real newlines there. Whoever ran /vaga almost certainly pasted the requirements from a job-board page, and browsers flatten <li> list items into one line with spaces when you copy them. The bot itself was passing the string straight through — nothing to fix in the formatting logic, the input channel just couldn't carry multi-line text.

Fix

descricao is now collected via a Modal with a paragraph-style text input (TextInputStyle.Paragraph), which does support real line breaks. Flow: /vaga titulo:... url:... modalidade:... senioridade:... → modal popup for descrição → existing preview/confirm/publish flow continues unchanged.

Test plan

• 3 new tests: modal shown before any lookups, real line breaks preserved end-to-end in the published message, timeout on modal submission does nothing further
• All 4 existing tests updated for the new modal-based interaction shape, still passing
• npx jest src/functions/general/commands/vaga.spec.ts — 7/7 passing
• Full bot package suite — 2851/2852 passing (1 pre-existing skip, unrelated)
• tsc --noEmit clean (full monorepo typecheck via pre-commit hook)
• eslint clean (pre-existing complexity warning on execute, 17→18, not newly introduced — already over budget before this change)

---

Summary by cubic

Fixes /vaga so the job description is collected via a modal with a paragraph field, preserving real line breaks. Published posts now render bullet lists correctly and avoid mixing fields across concurrent runs.

• Bug Fixes
  • Collect descricao via a modal (TextInputStyle.Paragraph) instead of a single-line option.
  • Keep the preview/confirm/publish flow; replies now come from the modal submission interaction.
  • Scope the modal to the current invocation using a unique customId and filter on user + customId, rejecting stale/concurrent submissions.
  • Handle modal submit timeout gracefully (no follow-ups if the user doesn’t submit).
  • Validate preview length and show an error if it exceeds 2000 characters.

^{Written for commit a5dbe9b. Summary will update on new commits.}

Summary by CodeRabbit

• New Features

  • The /vaga command now collects the “Descrição / requisitos” field through a modal, making it easier to enter longer text.
  • Multiline descriptions are preserved as typed in the preview and published message.

• Bug Fixes

  • Added safer handling when the description step times out, preventing an incomplete post from being published.
  • Improved the preview flow so publishing and cancel actions continue to work smoothly after submission.

[coderabbitai]

📝 Walkthrough

Walkthrough

The /vaga command now collects the job description through a Discord modal instead of a required slash-command string option. A modal builder and submission-awaiting helper were added, execution flow was updated to read descricao from modal fields, and reply/editReply calls now target the modal submission. Tests were updated accordingly.

Changes

Vaga Modal Flow

Layer / File(s)	Summary
Modal builder and collection helper packages/bot/src/functions/general/commands/vaga.ts	Adds ModalBuilder/TextInputBuilder imports and implements buildDescricaoModal() and collectDescricao() to show a modal and await the invoking user's submission with a timeout.
Command option removal and execution wiring packages/bot/src/functions/general/commands/vaga.ts	Removes the required descricao string option from the SlashCommandBuilder and updates execution to retrieve descricao from modalSubmit.fields after calling collectDescricao(chat).
Reply target switch to modalSubmit packages/bot/src/functions/general/commands/vaga.ts	Switches preview-too-long, initial preview, and timeout reply/editReply calls from chat to modalSubmit.
Test mocks and coverage for modal flow packages/bot/src/functions/general/commands/vaga.spec.ts	Updates makeInteraction to mock showModal/awaitModalSubmit/modalSubmit, and adds tests for modal invocation, multiline descricao preservation, and timeout rejection behavior.

Estimated code review effort: 2 (Simple) | ~15 minutes

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant ChatInteraction as chat
  participant ModalSubmit as modalSubmit
  participant Send as send

  User->>ChatInteraction: invoke /vaga
  ChatInteraction->>ChatInteraction: collectDescricao(chat)
  ChatInteraction->>ChatInteraction: showModal(buildDescricaoModal)
  ChatInteraction-->>ModalSubmit: awaitModalSubmit
  alt modal submitted
    ModalSubmit->>ModalSubmit: getTextInputValue('descricao')
    ModalSubmit->>ModalSubmit: reply(preview + buttons)
    ModalSubmit->>Send: publish job message
  else timeout/dismissed
    ModalSubmit->>ModalSubmit: editReply(clear components)
  end

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly states the main change: /vaga now collects descricao via a modal instead of a single-line option.

✨ 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 fix/vaga-descricao-modal

---

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

[github-actions]

Failed to generate code suggestions for PR

[github-actions]

	Warnings
⚠️	User-facing change without a CHANGELOG.md update. Add a line under ## [Unreleased] if this should appear in release notes. (Or apply the skip-changelog label if this PR does not affect end users.)

Generated by 🚫 dangerJS against a5dbe9b

[coderabbitai]

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@packages/bot/src/functions/general/commands/vaga.ts`:
- Around line 72-84: The modal collector in collectDescricao is too broad
because it only filters by user.id, so concurrent /vaga flows can resolve the
wrong submission. Update buildDescricaoModal and collectDescricao to generate a
unique customId per invocation, then make awaitModalSubmit filter on both the
current chat.user.id and that customId before reading
getTextInputValue('descricao'). Ensure the modal shown by chat.showModal uses
the same per-invocation customId.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: add4ad58-26b6-48f3-abd2-e6093c907490

📥 Commits

Reviewing files that changed from the base of the PR and between af5df5c and 4254ed9.

📒 Files selected for processing (2)

• packages/bot/src/functions/general/commands/vaga.spec.ts
• packages/bot/src/functions/general/commands/vaga.ts

[cubic-dev-ai]

1 issue found across 2 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 2 files (changes from recent commits).

<sub>Auto-approved: Fixes /vaga command to use a modal for multiline job descriptions, preserving line breaks. Changes are isolated to this command, well-tested, and low-risk.

Re-trigger cubic</sub>

[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