fix(api): add missing extensions to the meter v3 API

[tothandras]

Summary by CodeRabbit

Release Notes

• Documentation

  • Updated API specification for meters operations (create, get, list, delete).

• Refactor

  • Optimized internal field prefix processing logic.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR makes three distinct updates: removes a guard condition in a field-prefix grouping rule, adds extension annotations (unstable and internal) to meter operations, and updates the embedded Swagger specification in the generated API file.

Changes

Cohort / File(s)	Summary
Rule logic cleanup api/spec/lib/rules/field-prefix.js	Removed unnecessary guard preventing empty prefixes from being processed; prefix-grouping logic remains functionally equivalent.
API spec annotations api/spec/src/v3/meters/operations.tsp	Added @extension(Shared.UnstableExtension, true) and @extension(Shared.InternalExtension, true) decorators to each of the four meter operations (create, get, list, delete).
Generated API code api/v3/api.gen.go	Replaced embedded base64-encoded gzipped Swagger specification chunks; surrounding deserialization logic and GetSwagger behavior unchanged.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• api/v3/api.gen.go: Requires careful verification of the Swagger spec content changes—what exactly changed in the generated spec and why.
• api/spec/src/v3/meters/operations.tsp: Verify that both extensions are applied consistently across all four operations and that the annotations don't introduce unintended side effects.
• api/spec/lib/rules/field-prefix.js: Confirm the guard removal doesn't cause regressions with edge cases or empty inputs.

Possibly related PRs

• fix(api): typespec types #2545: Directly modifies embedded swaggerSpec content in generated API files using the same base64-encoded chunk replacement approach.
• chore: hide deprecated APIs from docs #3635: Adds internal/extension annotations to operation declarations in API spec files (.tsp), same type of metadata changes.
• fix(api): linter #3703: Touches the field-prefix.js rule file, modifying the repeated-prefix grouping logic.

Suggested reviewers

• chrisgacsal
• gergely-kurucz-konghq

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding missing extensions to the meter v3 API, which is the primary focus across the modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/api-meter-extensions

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c8488ca and 9e26561.

⛔ Files ignored due to path filters (1)

• api/v3/openapi.yaml is excluded by !**/openapi.yaml

📒 Files selected for processing (3)

• api/spec/lib/rules/field-prefix.js (0 hunks)
• api/spec/src/v3/meters/operations.tsp (4 hunks)
• api/v3/api.gen.go (1 hunks)

💤 Files with no reviewable changes (1)

• api/spec/lib/rules/field-prefix.js

🧰 Additional context used

📓 Path-based instructions (2)

**/*.go

⚙️ CodeRabbit configuration file

**/*.go: In general when reviewing the Golang code make readability and maintainability a priority, even potentially suggest restructuring the code to improve them.

Performance should be a priority in critical code paths. Anything related to event ingestion, message processing, database operations (regardless of database) should be vetted for potential performance bottlenecks.

Files:

• api/v3/api.gen.go

**/*.tsp

⚙️ CodeRabbit configuration file

**/*.tsp: Review the TypeSpec code for conformity with TypeSpec best practices. When recommending changes also consider the fact that multiple codegeneration toolchains depend on the TypeSpec code, each of which have their idiosyncrasies and bugs.

The declared API should be accurate, in parity with the actual implementation, and easy to understand for the user.

Files:

• api/spec/src/v3/meters/operations.tsp

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: Lint
• GitHub Check: Build
• GitHub Check: Code Generators
• GitHub Check: Artifacts / Container image
• GitHub Check: Migration Checks
• GitHub Check: Test
• GitHub Check: Repository Scan
• GitHub Check: Analyze (go)

🔇 Additional comments (3)

api/v3/api.gen.go (1)

1929-2062: Generated code reflects TypeSpec changes — looks good!

The updated embedded swagger spec is the expected output from regenerating after adding the UnstableExtension and InternalExtension annotations to the meter operations. Since this file is auto-generated and marked with "DO NOT EDIT", no manual changes should be made here.

api/spec/src/v3/meters/operations.tsp (2)

35-36: Consistent extension application across all meter operations.

The same @extension(Shared.UnstableExtension, true) and @extension(Shared.InternalExtension, true) annotations are applied to get, list, and delete operations. This ensures all meter endpoints are uniformly marked as unstable and internal.

Also applies to: 47-48, 59-60

---

23-24: Extensions properly defined and consistently applied — solid fix!

All four meter operations now have the UnstableExtension and InternalExtension annotations correctly in place. The extensions are properly defined in the shared module as "x-unstable" and "x-internal", and the pattern here matches what's already being used across the rest of the v3 API (subscriptions, events, entitlements, customers). Clean and consistent approach.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}