Skip to content

Mark the registration Nome field as required in its label (#255)#261

Merged
fabiodalez-dev merged 1 commit into
mainfrom
fix/registration-nome-asterisk
Jul 17, 2026
Merged

Mark the registration Nome field as required in its label (#255)#261
fabiodalez-dev merged 1 commit into
mainfrom
fix/registration-nome-asterisk

Conversation

@fabiodalez-dev

Copy link
Copy Markdown
Owner

The public registration form enforces nome as required (the HTML required attribute and the server-side check both do), but its label was missing the * indicator that Email and the toggle-driven Cognome/Telefono/Indirizzo already show — so the field looked optional while it wasn't.

Added the asterisk to match the profile and admin user forms, which already mark it. One-line view change; verified the /registrati form now renders "Nome *".

Reported by @Himura2la on #255.

The public registration form enforces nome as required (the HTML required
attribute and the server-side check both do), but its label was missing the *
indicator that Email and the toggle-driven Cognome/Telefono/Indirizzo already
show — so the field looked optional while it wasn't. Added the asterisk to match
the profile and admin user forms, which already mark it. Reported by Himura2la
on #255.
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@fabiodalez-dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ef8ba9a9-1da4-49ac-ba83-6994d8ccb1b0

📥 Commits

Reviewing files that changed from the base of the PR and between 36df4fe and b4e1258.

📒 Files selected for processing (1)
  • app/Views/auth/register.php
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/registration-nome-asterisk

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.

@fabiodalez-dev
fabiodalez-dev merged commit 91e0b0b into main Jul 17, 2026
6 checks passed
@fabiodalez-dev
fabiodalez-dev deleted the fix/registration-nome-asterisk branch July 17, 2026 14:37
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.

1 participant