feat: Show keyId after creating a new key#2107
Conversation
|
|
@harshsbhat is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughWalkthroughThe changes in this pull request enhance the Changes
Assessment against linked issues
Recent review detailsConfiguration used: CodeRabbit UI Files selected for processing (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! 🙏 |
chronark
left a comment
There was a problem hiding this comment.
I think this placement may be too confusing. We already observe users mixing up key and keyId and displaying it with equal hierarchy will likely just amplify this.
A better place would be where the apiId is displayed right now, but that requires reworking the layout
What do you think about this one? |
|
that works 👍 |
|
@chronark |
|
I don't think that would cause consistency issues, what is your concern? |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|



What does this PR do?
Fixes #2106
It displays the keyId after creating a new key.

Type of change
How should this be tested?
Checklist
Required
pnpm buildpnpm fmtconsole.logsgit pull origin mainAppreciated
Summary by CodeRabbit
CreateKeycomponent.Codecomponent for improved clarity.