Skip to content

[docs] include only User and System parts of the API docs #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 17, 2025

Conversation

capcom6
Copy link
Member

@capcom6 capcom6 commented May 17, 2025

Summary by CodeRabbit

  • Chores
    • Updated Swagger documentation generation to filter by "User" and "System" tags.

Copy link

coderabbitai bot commented May 17, 2025

Walkthrough

The Swagger documentation generation command in the codebase was updated to include filtering by the "User" and "System" tags. No other changes were made to the code or public entity declarations.

Changes

File(s) Change Summary
pkg/swagger/swagger.go Updated the go:generate directive to add --tags=User,System for Swagger doc generation.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GoGenerate
    participant SwaggerInit

    Developer->>GoGenerate: Run go generate
    GoGenerate->>SwaggerInit: Generate docs with --tags=User,System
    SwaggerInit-->>GoGenerate: Output filtered Swagger documentation
    GoGenerate-->>Developer: Generation complete
Loading
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch docs/limit-api-docs-tags
  • Post Copyable Unit Tests in Comment

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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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 generate unit tests to generate unit tests 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.

Copy link

@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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 37730e6 and 6d0e3f1.

📒 Files selected for processing (1)
  • pkg/swagger/swagger.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Build / Docker image (linux/arm64)
  • GitHub Check: Build / Docker image (linux/amd64)
  • GitHub Check: Analyze (go)

@@ -2,7 +2,7 @@ package swagger

import "embed"

//go:generate swag init --parseDependency --outputTypes json,yaml -d ../../ -g ./cmd/sms-gateway/main.go -o ../../pkg/swagger/docs
//go:generate swag init --parseDependency --tags=User,System --outputTypes json,yaml -d ../../ -g ./cmd/sms-gateway/main.go -o ../../pkg/swagger/docs
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

❓ Verification inconclusive

Approve: Updated Swagger directive; regenerate docs
Including --tags=User,System correctly narrows the generated API docs to only the “User” and “System” endpoints as per the PR objective. To apply this change, please run go generate ./pkg/swagger (or your CI script) to regenerate the JSON/YAML under pkg/swagger/docs, then commit those updated files so your docs hosting/CI reflects the filter.


🏁 Script executed:

#!/bin/bash
# Regenerate Swagger docs to reflect the new tag filter
go generate ./pkg/swagger

Length of output: 118


Error regenerating Swagger docs: missing swag CLI
The go:generate directive in pkg/swagger/swagger.go:5 failed with “exec: ‘swag’: executable file not found in $PATH”. To fix and commit your filtered docs:

• Install the Swag CLI:

go install github.com/swaggo/swag/cmd/swag@latest

• Ensure your $GOBIN (or $GOPATH/bin) is in your PATH.
• Re-run and commit the outputs:

go generate ./pkg/swagger
git add pkg/swagger/docs
git commit -m "chore: regenerate Swagger docs with User,System tags"
🤖 Prompt for AI Agents
In pkg/swagger/swagger.go at line 5, the go:generate directive was updated to
filter Swagger docs by User and System tags, but the Swagger docs were not
regenerated due to the missing swag CLI tool. To fix this, install the swag CLI
by running 'go install github.com/swaggo/swag/cmd/swag@latest', ensure your Go
bin directory is in your PATH, then run 'go generate ./pkg/swagger' to
regenerate the docs, and finally commit the updated files under
pkg/swagger/docs.

@capcom6 capcom6 merged commit 99791de into master May 17, 2025
10 checks passed
@capcom6 capcom6 deleted the docs/limit-api-docs-tags branch May 17, 2025 03:47
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.

1 participant