Skip to content

fix(home): precise readiness mail-warning wording (#4297 Node half)#3861

Merged
PierreBrisorgueil merged 1 commit into
masterfrom
fix/4297-readiness-mail-wording
Jun 13, 2026
Merged

fix(home): precise readiness mail-warning wording (#4297 Node half)#3861
PierreBrisorgueil merged 1 commit into
masterfrom
fix/4297-readiness-mail-wording

Conversation

@PierreBrisorgueil

Copy link
Copy Markdown
Contributor

Summary

Node half of #4297 (the Vue half — dropping the redundant admin mailer banner — ships in the Vue admin/account UX PR). The admin Readiness tab is now the single home for the "no mailer" signal, so its wording carries the consequence:

  • modules/home/services/home.service.js — the mail readiness check's warning message becomes No mail provider configured — users register without email verification (the ok-branch message Mail provider configured is unchanged).

Test plan

home.service.unit 12/12, full home module 31/31 (the integration test's pinned category order ['config','security','auth','mail','billing','analytics','errorTracking'] is untouched). Lint clean.

refs pierreb-devkit/Vue#4297

With the admin layout banner removed on the UI side, the readiness 'mail'
row is the single signal for an unconfigured mailer — its warning message
now carries the consequence wording (users register without email
verification) instead of relying on a separate banner. The ok-branch
message and the category order are unchanged.

refs pierreb-devkit/Vue#4297
Copilot AI review requested due to automatic review settings June 13, 2026 16:52
@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@PierreBrisorgueil, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 52 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: db91aa11-9c08-4802-b476-3642a3177274

📥 Commits

Reviewing files that changed from the base of the PR and between 7d4f605 and 5b9b641.

📒 Files selected for processing (2)
  • modules/home/services/home.service.js
  • modules/home/tests/home.service.unit.tests.js
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/4297-readiness-mail-wording

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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the admin “Readiness” mail check warning to explicitly describe the user-facing consequence when no mail provider is configured, and adds unit coverage to lock the wording in.

Changes:

  • Updates the mail readiness warning message to: No mail provider configured — users register without email verification.
  • Adds unit tests covering both the warning (no mailer) and ok (mailer configured) mail readiness messages.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
modules/home/services/home.service.js Updates the mail readiness warning message to include the consequence when mail is not configured.
modules/home/tests/home.service.unit.tests.js Adds unit tests to assert the updated warning wording and ensure the ok message remains unchanged.

@codecov

codecov Bot commented Jun 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.41%. Comparing base (7d4f605) to head (5b9b641).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3861   +/-   ##
=======================================
  Coverage   92.41%   92.41%           
=======================================
  Files         162      162           
  Lines        5394     5394           
  Branches     1736     1735    -1     
=======================================
  Hits         4985     4985           
  Misses        328      328           
  Partials       81       81           
Flag Coverage Δ
integration 60.10% <100.00%> (ø)
unit 73.17% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7d4f605...5b9b641. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

2 participants