Bug Fix: Improved full-width layout and text truncation to prevent overlap with button
What does this PR do?
Added w-full to ensure the container takes the full width and added a max-w-[calc(100%-32px)] to the span containing permission.name to prevent it from overlapping with the button.
Fixes #2348
Type of change
- [X] Bug fix (non-breaking change which fixes an issue)
- [ ] Chore (refactoring code, technical debt, workflow improvements)
- [ ] Enhancement (small improvements)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update
How should this be tested?
Just go to Authorization/Permissions/ and then go to particular permission.
Checklist
Required
- [x] Filled out the "How to test" section in this PR
- [x] Read Contributing Guide
- [x] Self-reviewed my own code
- [ ] Commented on my code in hard-to-understand areas
- [ ] Ran
pnpm build - [ ] Ran
pnpm fmt - [x] Checked for warnings, there are none
- [x] Removed all
console.logs - [x] Merged the latest changes from main onto my branch with
git pull origin main - [x] My changes don't cause any responsiveness issues
Appreciated
- [ ] If a UI change was made: Added a screen recording or screenshots to this PR
- [ ] Updated the Unkey Docs if changes were necessary
Summary by CodeRabbit
- New Features
- Improved layout and styling of the RolesPage component for better visual presentation of permissions.
- Enhanced tooltip functionality for displaying permission names with a copy button.
- Tooltip trigger area now occupies the full width of its container for better accessibility.
⚠️ No Changeset found
Latest commit: 2b628c4d227a0598ad1a5d79204e9b8d889c030f
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| dashboard | ✅ Ready (Inspect) | Visit Preview | 💬 1 unresolved ✅ 5 resolved |
Oct 24, 2024 1:25pm |
| engineering | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 24, 2024 1:25pm |
@adityaraj-09 is attempting to deploy a commit to the Unkey Team on Vercel.
A member of the Team first needs to authorize it.
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
Walkthrough
The pull request modifies the RolesPage component located in apps/dashboard/app/(app)/authorization/permissions/[permissionId]/page.tsx. Key changes include the addition of a w-full class to the div wrapping the TooltipTrigger, ensuring full width occupancy. The previous w-full class was removed from the TooltipTrigger. Additionally, the span displaying permission.name now includes a max-w-[calc(100%-32px)] class for better layout management. The overall logic and control flow of the component remain unchanged.
Changes
| File | Change Summary |
|---|---|
| apps/dashboard/app/(app)/authorization/permissions/[permissionId]/page.tsx | Updated the layout of the TooltipTrigger and permission.name display in the RolesPage component. |
Assessment against linked issues
| Objective | Addressed | Explanation |
|---|---|---|
| The copy icon should remain on the right side of the permission name (2348) | ✅ |
Possibly related PRs
- #2071: This PR modifies the
RolesPagecomponent to enhance the user interface by integrating a tooltip feature around the permission name display, which is directly related to the changes made in the main PR regarding theTooltipTriggerand layout adjustments. - #2253: This PR also modifies the
RolesPagecomponent, specifically updating theTooltipTriggerto use theasChildprop, which is relevant to the changes in the main PR that involve layout enhancements around the tooltip functionality.
Suggested labels
Bug, 🕹️ oss.gg, :joystick: 150 points
Suggested reviewers
- mcstepp
- chronark
- perkinsjr
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?
🪧 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
@coderabbitaiin 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
@coderabbitaiin 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 pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.
Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Here is an example:
<type>[optional scope]: <description>
fix: I fixed something for Unkey
Details:
No release type found in pull request title "Bug Fix: Improved full-width layout and text truncation to prevent overlap with button". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
/assign
This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest
please sign the CLA and fix the pr title
Awarding adityaraj-09: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/adityaraj-09