-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor: Rename "More info dialog" to "Details view" for clearer tra… #22537
base: dev
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Hi 👋 Thank you for the contribution. The "more info" terms is well know for HA users. It's not something we can change easily. I agree "more info dialog" is not a good term. I will discuss that point with the UX/UI team. Also, "detail view" is not the right term because we already have "view" in the dashboard and it's another element. |
Hi @piitaya , There is a concern about using "detail view" due to the existing. Perhaps we can brainstorm alternatives that avoid confusion, a more accurate description than the "view" terminal while still pro "more info dialog." I’d be happy to collaborate on finding a term that is both user-familiar and clear. I'm looking forward to hearing your thoughts! |
Co-authored-by: Bram Kragten <[email protected]>
For issue #22517, here’s a PR description that aligns with the requested format:
Breaking change
Proposed change
This PR renames the "More info dialog" to "Details view" across the codebase to streamline terminology and simplify translations. This adjustment aligns with the naming conventions used in other components, providing a clearer and more cohesive user experience.
Type of change
Example configuration
Additional information
Checklist
If user-exposed functionality or configuration variables are added/changed:
Additional Information
This PR fixes or closes issue: Resolves #22517
Documentation Impact: Documentation changes may not be needed as this only affects UI terminology. However, if deemed necessary, I’m available to contribute to the required documentation updates.
Contributor GitHub: @iemafzalhassan