fix: deduplicate operationIds

[chronark]

Summary by CodeRabbit

• Documentation
  • Updated API route metadata for key verification endpoint.
  • Refined operation ID naming convention.
  • Added metadata property for enhanced API documentation.
• Chores
  • Reformatted package.json files for various packages to improve readability.

[vercel]

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	Jan 13, 2025 2:27pm
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 13, 2025 2:27pm
play	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 13, 2025 2:27pm
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 13, 2025 2:27pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8f0d4a3

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces metadata modifications to the API route handling key verifications. The changes involve updating the operationId to a more structured naming format and adding an x-speakeasy-name-override property. These modifications are purely related to API documentation and naming conventions, with no impact on the actual functionality of the endpoint.

Changes

File	Change Summary
apps/api/src/routes/v1_keys_getVerifications.ts	- Updated operationId from "getVerifications" to "keys.getVerifications" - Added x-speakeasy-name-override property with value "getVerifications"
packages/api/package.json	- Reformatted keywords and files fields from multi-line to single-line structure.
packages/hono/package.json	- Reformatted keywords and files fields from multi-line to single-line structure.
packages/nextjs/package.json	- Reformatted keywords and files fields from multi-line to single-line structure.
packages/ratelimit/package.json	- Reformatted keywords and files fields from multi-line to single-line structure.

Possibly related PRs

• feat: allow-developer-to-set-a-custom-refill-time-when-using-the #2114: This PR modifies the verifyKey route in v1_keys_verifyKey.ts, which is related to the changes in the v1_keys_getVerifications.ts file where the operationId was updated. Both PRs involve key verification processes.
• feat: Who Am I route #2159: The introduction of the whoami route in v1_keys_whoAmI.ts and related files may share context with the getVerifications functionality, as both are part of the key management API.
• feat: add more cloudflare ratelimits #2636: The changes in env.ts related to rate limits may connect with the getVerifications route, as both involve rate limiting configurations.

Suggested reviewers

• mcstepp
• perkinsjr
• MichaelUnkey
• ogzhanolguncu

---

📜 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 849b6f3 and 8f0d4a3.

📒 Files selected for processing (4)

• packages/api/package.json (1 hunks)
• packages/hono/package.json (1 hunks)
• packages/nextjs/package.json (1 hunks)
• packages/ratelimit/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• packages/nextjs/package.json
• packages/ratelimit/package.json
• packages/api/package.json
• packages/hono/package.json

⏰ Context from checks skipped due to timeout of 90000ms (17)

• GitHub Check: Test Packages / Test ./packages/rbac
• GitHub Check: Test Packages / Test ./packages/nextjs
• GitHub Check: Test Packages / Test ./packages/hono
• GitHub Check: Test Packages / Test ./packages/cache
• GitHub Check: Test Packages / Test ./packages/api
• GitHub Check: Test Packages / Test ./internal/clickhouse
• GitHub Check: Test Packages / Test ./internal/resend
• GitHub Check: Test Packages / Test ./internal/keys
• GitHub Check: Test Packages / Test ./internal/id
• GitHub Check: Test Packages / Test ./internal/hash
• GitHub Check: Test Packages / Test ./internal/encryption
• GitHub Check: Test Packages / Test ./internal/billing
• GitHub Check: Test API / API Test Local
• GitHub Check: Build / Build
• GitHub Check: Test Agent Local / test_agent_local
• GitHub Check: autofix
• GitHub Check: Analyze (javascript-typescript)

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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]

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