BUGFIX/SN-352 : making account name to max 60 length

[aaradhya-egov]

Choose the appropriate template for your PR:

Feature PR

Feature Request

JIRA ID

Module

Description

Related Issues

---

Bugfix PR

Bugfix Request

JIRA ID

Module

Description

Root Cause

Related Issues

---

Release PR

Summary by CodeRabbit

• New Features
  • Enhanced validation for the account name input field with a maximum length of 60 characters.
  • Added a tooltip reference for the account name input, providing additional guidance to users.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the sign-up configuration file, specifically adding validation and informational properties to the account name input field. The changes include setting a maximum length of 60 characters for the account name and introducing an information message tooltip reference, which aims to enhance user input validation and provide additional guidance during the sign-up process.

Changes

File	Change Summary
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/SignUp/config.js	Added maxLength: 60 and infoMessage: "SANDBOX_SIGNUP_ACCOUNT_NAME_TOOLTIP" to the accountName input field in SignUpConfig

Suggested Reviewers

• jagankumar-egov

Poem

🐰 A rabbit's tale of sign-up delight,
Sixty characters, a validation's might!
Tooltips dancing, guiding the way,
Account names trimmed with care today,
A config change, simple and bright! 🖥️

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0113cea and 8274b3d.

📒 Files selected for processing (1)

• micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/SignUp/config.js (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/SignUp/config.js (1)

Pattern **/*.js: check

🔇 Additional comments (2)

micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/SignUp/config.js (2)

32-32: Good enhancement for input validation.

Adding a maximum length of 60 ensures that overly long names are restricted, which can prevent potential UI overflow or database issues. The limit seems reasonable for typical user account names.

---

32-32: Informative tooltip is beneficial.

Providing infoMessage:"SANDBOX_SIGNUP_ACCOUNT_NAME_TOOLTIP" helps guide the user. Verify that the tooltip text is sufficiently descriptive and localized if the application supports multiple languages.

[coderabbitai]

🧹 Nitpick (assertive)

Consider allowing a broader character set if needed.

The regex pattern currently only allows letters and spaces. If users might have names with accents, apostrophes, hyphens, or other characters, consider adjusting the regex to support those characters as well.