Skip to content

fix: adding apiId field to verify key code snippet#2940

Merged
chronark merged 1 commit intounkeyed:mainfrom
Nelwhix:improving-verify-key-example
Mar 8, 2025
Merged

fix: adding apiId field to verify key code snippet#2940
chronark merged 1 commit intounkeyed:mainfrom
Nelwhix:improving-verify-key-example

Conversation

@Nelwhix
Copy link
Contributor

@Nelwhix Nelwhix commented Mar 8, 2025

What does this PR do?

This PR adds apiId field to the verifyKey curl request in creating a root key and creating keys under an API page

Fixes # (issue)
#2937

Type of change

  • 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?

Screenshot 2025-03-08 at 15-39-52 Open Source API Authentication

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • 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
    • Enhanced API key verification by enriching the data payload with an associated API identifier. This update provides additional context during key verification while maintaining the existing user workflow.

@changeset-bot
Copy link

changeset-bot bot commented Mar 8, 2025

⚠️ No Changeset found

Latest commit: e4c73f6

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

@vercel
Copy link

vercel bot commented Mar 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 8, 2025 2:53pm
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 8, 2025 2:53pm
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 8, 2025 2:53pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 8, 2025 2:53pm

@vercel
Copy link

vercel bot commented Mar 8, 2025

@Nelwhix is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 8, 2025

📝 Walkthrough

Walkthrough

This pull request updates two components that construct curl command snippets for key verification. Both components now include an additional "apiId" field in the JSON payload alongside the existing "key" field. The changes solely extend the payload without altering the underlying logic or control flow.

Changes

File(s) Change Summary
apps/dashboard/.../client.tsx
apps/dashboard/.../keys.tsx
Updated curl command snippets to include the "apiId" field in the JSON payload along with the "key".

Possibly related PRs

Suggested labels

Feature

Suggested reviewers

  • mcstepp
  • chronark
  • perkinsjr
  • MichaelUnkey

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 101d62e and e4c73f6.

📒 Files selected for processing (2)
  • apps/dashboard/app/(app)/apis/[apiId]/keys/[keyAuthId]/new/client.tsx (1 hunks)
  • apps/dashboard/app/new/keys.tsx (1 hunks)
🔇 Additional comments (2)
apps/dashboard/app/new/keys.tsx (1)

76-79: Added apiId to the verifyKey curl request. LGTM!

This enhances the functionality of the verifyKey curl request by adding the necessary apiId field to the JSON payload, which addresses issue #2937. The change ensures the verification endpoint has both the key and its associated API ID for proper validation.

apps/dashboard/app/(app)/apis/[apiId]/keys/[keyAuthId]/new/client.tsx (1)

149-152: Added apiId to the verification snippet. LGTM!

This change properly adds the apiId field to the JSON payload, ensuring consistency with the change in the keys.tsx file and addressing issue #2937. The curl command now includes all necessary fields for proper key verification.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @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.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2025

Thank you for following the naming conventions for pull request titles! 🙏

@chronark
Copy link
Collaborator

chronark commented Mar 8, 2025

ooh very nice, thank you!

@vercel vercel bot temporarily deployed to Preview – engineering March 8, 2025 14:49 Inactive
@vercel vercel bot temporarily deployed to Preview – play March 8, 2025 14:50 Inactive
@vercel vercel bot temporarily deployed to Preview – www March 8, 2025 14:51 Inactive
@vercel vercel bot temporarily deployed to Preview – dashboard March 8, 2025 14:53 Inactive
@chronark chronark merged commit 92624a2 into unkeyed:main Mar 8, 2025
26 of 28 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jul 2, 2025
13 tasks
@coderabbitai coderabbitai bot mentioned this pull request Aug 22, 2025
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants