Use readonly inputs for current values of Email and PhoneNumber on settings page of Boilerplate (#9601)

[msynk]

closes #9601

Summary by CodeRabbit

• UI Improvements
  • Updated email display in settings to use a read-only text field instead of a tag
  • Updated phone number display in settings to use a read-only text field instead of a tag

The changes enhance the visual presentation of user contact information while maintaining the existing functionality.

[coderabbitai]

Walkthrough

The pull request modifies the display of email and phone number in the Boilerplate project template's settings pages. In both ChangeEmailSection.razor and ChangePhoneNumberSection.razor, the rendering of contact information has been updated from using a BitTag component to a BitTextField component in read-only mode. This change aims to make the current email and phone number values more easily selectable by users, transitioning from a tag-like display to a text field representation.

Changes

File	Change Summary
.../ChangeEmailSection.razor	Replaced BitTag with read-only BitTextField for email display
.../ChangePhoneNumberSection.razor	Replaced BitTag with read-only BitTextField for phone number display

Assessment against linked issues

Objective	Addressed	Explanation
Make Email and PhoneNumber values selectable [#9601]	✅

Poem

🐰 A rabbit's tale of UI delight,
Text fields now shine so crisp and bright,
From tags to fields, a smooth transition,
Selecting text becomes our mission!
Hop, hop, hooray for user's might! 🔤

---

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: 0

🧹 Nitpick comments (1)

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Authorized/Settings/ChangeEmailSection.razor (1)

13-13: Add a label for better user clarity.

Currently, the read-only field displays the email without indicating that it is the "Current Email." Adding a descriptive label would improve the user experience and clarity.

Here’s a possible improvement:

- <BitTextField ReadOnly Value="@Email" />
+ <BitTextField
+     ReadOnly
+     Value="@Email"
+     Label="@Localizer[nameof(AppStrings.CurrentEmail)]" />

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between be736ff and 1468542.

📒 Files selected for processing (2)

• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Authorized/Settings/ChangeEmailSection.razor (1 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Authorized/Settings/ChangePhoneNumberSection.razor (1 hunks)

🔇 Additional comments (1)

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Authorized/Settings/ChangePhoneNumberSection.razor (1)

13-13: Readonly text field properly meets the PR goal.

This is a good improvement from a usability perspective, allowing easy copying while preventing unintended edits. Looks consistent with the PR’s objective of using a readonly input for the existing phone number.