Validate Organization Name on Frontend During Signup

[abimaelmartell]

Description 📣

This PR improves organization name validation during the signup flow by extracting the logic into a reusable utility function. It also replaces the boolean error flag with a more informative error message, improving user feedback.

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

No automated tests were added since this change affects only client-side form validation and UI messaging. Let me know if you'd like me to add unit tests for the validator function.

# Steps to reproduce:
1. Go to the signup page
2. Leave the organization name field empty and try to submit – should show "Please enter your organization name"
3. Enter invalid characters like `!@#$`, should show an error about allowed characters
4. Enter a valid name, form should proceed without error

Should fix #3867

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[maidul98]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[greptile-apps]

PR Summary

Adding frontend organization name validation during signup with potential security concerns in regex implementation.

• New validateOrganizationName utility potentially vulnerable to ReDoS attacks due to using native regex instead of RE2 package for validation, needs security review
• Organization name validation message states dashes (-) but implementation allows underscores (_), causing documentation/implementation mismatch
• Error state in UserInfoStep.tsx changed from boolean to string|null improving UX with specific error messages
• Consider adding unit tests despite being UI changes to ensure validation edge cases are covered

_{2 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: ReDoS vulnerability risk. Replace with RE2 package for safer regex validation as per Rule 1