chore: Added inline style elements to keep the view and copy btns visible when keys longer than 87 characters. #2606
Conversation
… visible even with api keys longer than 87 characters
… visible even with api keys longer than 87 characters and did pnpm build and pnpm fmt
|
|
|
|
@akash-2004 is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
📝 Walkthrough📝 WalkthroughWalkthroughThe changes in this pull request primarily focus on the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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 (
|
|
Thank you for following the naming conventions for pull request titles! 🙏 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
- apps/dashboard/app/(app)/apis/[apiId]/keys/[keyAuthId]/new/client.tsx (1 hunks)
🔇 Additional comments (1)
apps/dashboard/app/(app)/apis/[apiId]/keys/[keyAuthId]/new/client.tsx (1)
288-298: LGTM! The styling changes effectively handle long keys.
The implementation successfully prevents the view and copy buttons from being pushed out of view when keys are longer than 87 characters by properly handling text overflow.
apps/dashboard/app/(app)/apis/[apiId]/keys/[keyAuthId]/new/client.tsx
Outdated
Show resolved
Hide resolved
…e view and copy btns always visible even with long api key
1ef7cf1 to
1e9bf70
Compare
|
I have added the KeyDisplay.module.css file and removed inline styling as suggested by the bot above. |
|
@chronark Would it be possible to get this merged? Actually this is my first time contributing and I am participating in the hacktoberfest. |
|
we're not going to accept non-tailwind solutions for this, as it adds too much techdebt for such a simple fix |
|
@chronark I will add tailwind solution then |
What does this PR do?
I added inline style elements to pre tag in client.tsx to keep the view and copy buttons visible even if the key is longer than 87 characters as before the key was pushing the buttons out and making them inaccessible as a result.
Before
After
Fixes # 2401
Type of change
How should this be tested?
-Notice that both view and copy buttons are visible, which previously they were not.
Checklist
Required
pnpm buildpnpm fmtconsole.logsgit pull origin mainAppreciated
Summary by CodeRabbit
New Features
Bug Fixes
Documentation