Skip to content

Conversation

@turip
Copy link
Member

@turip turip commented May 1, 2025

Overview

The API reference is hard to use given that generics Apps management and the APIs provided by different apps are merged together.

This patch improves the situation.

Summary by CodeRabbit

  • Documentation
    • Added new API tags "App: Custom Invoicing" and "App: Stripe" to improve categorization of invoicing and Stripe-related endpoints.
    • Retagged relevant API endpoints to use these new tags for clearer grouping in documentation and tooling.
    • Updated interface metadata to reflect new tagging without changing API behavior or structure.

@turip turip requested a review from a team as a code owner May 1, 2025 06:04
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 1, 2025

📝 Walkthrough

Walkthrough

This change introduces two new API tags, "App: Custom Invoicing" and "App: Stripe," to the OpenAPI specifications and related TypeSpec source files. Several existing API endpoints previously tagged as "Apps" are re-categorized under these more specific tags. Correspondingly, the embedded Swagger specification strings in both server and client Go code are updated to reflect these tagging changes. No API endpoint parameters, request/response schemas, or logic are altered; the updates affect only metadata used for API documentation and categorization.

Changes

File(s) Change Summary
api/openapi.yaml, api/openapi.cloud.yaml Added new tags "App: Custom Invoicing" and "App: Stripe" to global tags list. Updated tags on six API endpoints from "Apps" to these new tags. No functional changes to endpoints.
api/spec/src/app/custominvoicing.tsp Changed AppCustomInvoicing interface tag annotation from "Apps" to "App: Custom Invoicing".
api/spec/src/app/stripe.tsp Changed AppStripe interface tag annotation from "Apps" to "App: Stripe".
api/spec/src/cloud/main.tsp Added new tag metadata for "App: Custom Invoicing" and "App: Stripe". Updated tags on AppCustomInvoicing and AppStripe interfaces accordingly.
api/spec/src/main.tsp Added new tag metadata entries for "App: Custom Invoicing" and "App: Stripe" in the OpenMeter service declaration.
api/api.gen.go, api/client/go/client.gen.go Replaced embedded Swagger specification strings to reflect updated OpenAPI tags. No changes to code logic or API behavior.

Possibly related PRs

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

Error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2
Failed executing command with error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2


📜 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 76c5661 and ff2b15c.

📒 Files selected for processing (8)
  • api/api.gen.go (1 hunks)
  • api/client/go/client.gen.go (1 hunks)
  • api/openapi.cloud.yaml (7 hunks)
  • api/openapi.yaml (7 hunks)
  • api/spec/src/app/custominvoicing.tsp (1 hunks)
  • api/spec/src/app/stripe.tsp (1 hunks)
  • api/spec/src/cloud/main.tsp (2 hunks)
  • api/spec/src/main.tsp (1 hunks)
✅ Files skipped from review due to trivial changes (6)
  • api/spec/src/app/custominvoicing.tsp
  • api/spec/src/app/stripe.tsp
  • api/spec/src/main.tsp
  • api/client/go/client.gen.go
  • api/spec/src/cloud/main.tsp
  • api/openapi.cloud.yaml
🚧 Files skipped from review as they are similar to previous changes (2)
  • api/api.gen.go
  • api/openapi.yaml
⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: CI
  • GitHub Check: E2E
  • GitHub Check: Quickstart
  • GitHub Check: Developer environment
  • GitHub Check: Commit hooks
  • GitHub Check: Lint
  • GitHub Check: Test
  • GitHub Check: Build
  • GitHub Check: Analyze (go)
✨ 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

@turip turip requested a review from tothandras May 1, 2025 06:04
chrisgacsal
chrisgacsal previously approved these changes May 1, 2025
@chrisgacsal chrisgacsal added the release-note/bug-fix Release note: Bug Fixes label May 1, 2025
@turip turip added release-note/misc Miscellaneous changes and removed release-note/bug-fix Release note: Bug Fixes labels May 1, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
api/spec/src/app/custominvoicing.tsp (1)

53-56: ⚠️ Potential issue

Typo in method name: missing 'h'. The method draftSyncronized should be spelled draftSynchronized to match the path (/synchronized) and @operationId("appCustomInvoicingDraftSynchronized"). Please update:

-  draftSyncronized(
+  draftSynchronized(
🧹 Nitpick comments (2)
api/spec/src/app/custominvoicing.tsp (1)

71-74: Optional rename for consistency: Consider renaming paymentStatus to updatePaymentStatus to align with @operationId("appCustomInvoicingUpdatePaymentStatus") and the summary. This enhances clarity in generated clients:

-  paymentStatus(
+  updatePaymentStatus(
api/openapi.yaml (1)

11-13: Add description to the new global tag for consistency

Other tags in the global list (e.g., Subscriptions) include a description field. Please add a concise description to the App: Custom Invoicing tag so it renders uniformly in the API docs:

- name: 'App: Custom Invoicing'
  description: 'APIs to manage invoice drafts, issuance, and payment status for the Custom Invoicing app'
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 94a1de6 and 76c5661.

📒 Files selected for processing (3)
  • api/api.gen.go (1 hunks)
  • api/openapi.yaml (4 hunks)
  • api/spec/src/app/custominvoicing.tsp (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: Quickstart
  • GitHub Check: E2E
  • GitHub Check: CI
  • GitHub Check: Lint
  • GitHub Check: Developer environment
  • GitHub Check: Commit hooks
  • GitHub Check: Test
  • GitHub Check: Build
  • GitHub Check: Analyze (go)
🔇 Additional comments (6)
api/spec/src/app/custominvoicing.tsp (2)

47-47: Tag grouping applied correctly: The new @tag("App: Custom Invoicing") properly categorizes these endpoints under the Custom Invoicing group, improving the API reference structure as intended by the PR.


62-65: Method name misalignment: The method finalized doesn’t reflect its action (issuing/synchronized) and mismatches the @operationId. Rename it to something like issuingSynchronized:

-  finalized(
+  issuingSynchronized(

This keeps method names, routes, and operationIds in sync.

api/api.gen.go (1)

18865-18868: Confirm the embedded Swagger spec was properly regenerated
This file is auto-generated and contains the gzipped/base64 OpenAPI spec. After updating api/openapi.yaml and TypeSpec sources (to add the "App: Custom Invoicing" tag), you must rerun the standard generator (e.g., go generate ./api or make gen) rather than manually patching this blob.
Please verify:

  • The new tag appears in the decoded spec.
  • No manual edits remain—only machine-generated diffs.
api/openapi.yaml (3)

726-728: Custom tag correctly applied to the draft/synchronized endpoint

The tags block for the POST /api/v1/apps/custom-invoicing/{invoiceId}/draft/synchronized operation now references App: Custom Invoicing. Indentation and YAML syntax look correct.


791-793: Custom tag correctly applied to the issuing/synchronized endpoint

The tags list for POST /api/v1/apps/custom-invoicing/{invoiceId}/issuing/synchronized has been updated to use App: Custom Invoicing with proper indentation.


856-858: Custom tag correctly applied to the payment status endpoint

The tags section for POST /api/v1/apps/custom-invoicing/{invoiceId}/payment/status is now tagged App: Custom Invoicing as intended.

The API reference is hard to use given that generics Apps management and
the APIs provided by different apps are merged together.

This patch improves the situation.
@turip turip enabled auto-merge (squash) May 1, 2025 12:24
@turip turip merged commit faee429 into main May 1, 2025
28 checks passed
@turip turip deleted the docs/fix-api-grouping branch May 1, 2025 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-note/misc Miscellaneous changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants