Skip to content
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

feat(api): enhance business report endpoints with detailed metadata #3031

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

alonp99
Copy link
Collaborator

@alonp99 alonp99 commented Feb 5, 2025

  • Add descriptions and summaries to various Swagger operations
  • Improve response descriptions for better clarity and documentation

(your API documentation is so helpful, it could replace a user manual in a soap factory)

Summary by CodeRabbit

  • New Features

    • Enhanced several API endpoints with additional query parameters for improved filtering, pagination, and batch processing.
  • Documentation

    • Updated endpoint documentation with clear summaries and descriptions for successful and error responses to improve usability.

- Add descriptions and summaries to various Swagger operations
- Improve response descriptions for better clarity and documentation

(your API documentation is so helpful, it could replace a user manual in a soap factory)
Copy link

changeset-bot bot commented Feb 5, 2025

⚠️ No Changeset found

Latest commit: 6d6c0e6

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

Copy link
Contributor

coderabbitai bot commented Feb 5, 2025

Walkthrough

The changes enhance the API documentation in the BusinessReportControllerExternal by introducing several new methods and updating Swagger annotations. New endpoints include fetching, listing, and creating business reports, along with additional query parameters for filtering and pagination. The modifications also improve the response documentation through updated ApiOkResponse, ApiForbiddenResponse, and ApiBadRequestResponse annotations, and refine batch creation with ApiConsumes and ApiBody.

Changes

File(s) Change Summary
services/workflows-service/src/.../business-report.controller.external.ts - Added new methods: getLatestBusinessReport, listBusinessReports, listFindings, getMetrics, createBusinessReport, getBusinessReportById, createBusinessReportBatch
- Updated Swagger annotations (ApiOkResponse, ApiForbiddenResponse, ApiBadRequestResponse, ApiConsumes, ApiBody) to enhance endpoint documentation with clear summaries, descriptions, and response details.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Controller as BusinessReportControllerExternal
    participant Service as BusinessReportService

    Client->>Controller: GET /latest-business-report (with query params)
    Controller->>Service: Fetch latest business report
    Service-->>Controller: Report data
    Controller-->>Client: 200 OK with report data

    Client->>Controller: POST /create-business-report (Payload)
    Controller->>Service: Create business report
    Service-->>Controller: Confirmation/Details
    Controller-->>Client: 200 OK with created report
Loading

Possibly related PRs

Suggested reviewers

  • tomer-shvadron
  • MatanYadaev

Poem

I'm a happy bunny, hopping through code with glee,
New endpoints and clear docs, a sight for all to see.
Swagger shines bright with annotations neat and true,
Each method now steps in line, fresh as morning dew.
CodeRabbit cheers in ASCII art and emoji delight—
Leaping forward in our API, day and night!

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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
🪧 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.

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: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4517bac and 6d6c0e6.

📒 Files selected for processing (1)
  • services/workflows-service/src/business-report/business-report.controller.external.ts (6 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: test_windows
  • GitHub Check: test_linux
  • GitHub Check: build (windows-latest)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: lint
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (4)
services/workflows-service/src/business-report/business-report.controller.external.ts (4)

195-207: LGTM!

The Swagger documentation for this endpoint is complete and well-structured.


212-234: LGTM!

The Swagger documentation for this endpoint is complete and well-structured.


266-284: LGTM!

The Swagger documentation for this endpoint is complete and well-structured.


348-364: LGTM!

The Swagger documentation for this endpoint is complete and well-structured.

Comment on lines +101 to +114
@swagger.ApiOperation({
summary: 'List business reports',
description: 'Get a paginated list of business reports with optional filters',
})
@swagger.ApiQuery({
name: 'page',
required: false,
description: 'Pagination parameters',
})
@swagger.ApiQuery({
name: 'search',
required: false,
description: 'Search term to filter reports',
})
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Document all query parameters.

The endpoint accepts several query parameters that are not documented in the Swagger annotations. Add @ApiQuery decorators for: from, to, reportType, riskLevels, statuses, findings, and isAlert parameters.

  @swagger.ApiQuery({
    name: 'page',
    required: false,
    description: 'Pagination parameters',
  })
  @swagger.ApiQuery({
    name: 'search',
    required: false,
    description: 'Search term to filter reports',
  })
+ @swagger.ApiQuery({
+   name: 'from',
+   required: false,
+   description: 'Start date for filtering reports',
+ })
+ @swagger.ApiQuery({
+   name: 'to',
+   required: false,
+   description: 'End date for filtering reports',
+ })
+ @swagger.ApiQuery({
+   name: 'reportType',
+   required: false,
+   description: 'Type of reports to filter',
+ })
+ @swagger.ApiQuery({
+   name: 'riskLevels',
+   required: false,
+   description: 'Risk levels to filter by',
+ })
+ @swagger.ApiQuery({
+   name: 'statuses',
+   required: false,
+   description: 'Statuses to filter by',
+ })
+ @swagger.ApiQuery({
+   name: 'findings',
+   required: false,
+   description: 'Findings to filter by',
+ })
+ @swagger.ApiQuery({
+   name: 'isAlert',
+   required: false,
+   description: 'Filter by alert status',
+ })
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@swagger.ApiOperation({
summary: 'List business reports',
description: 'Get a paginated list of business reports with optional filters',
})
@swagger.ApiQuery({
name: 'page',
required: false,
description: 'Pagination parameters',
})
@swagger.ApiQuery({
name: 'search',
required: false,
description: 'Search term to filter reports',
})
@swagger.ApiOperation({
summary: 'List business reports',
description: 'Get a paginated list of business reports with optional filters',
})
@swagger.ApiQuery({
name: 'page',
required: false,
description: 'Pagination parameters',
})
@swagger.ApiQuery({
name: 'search',
required: false,
description: 'Search term to filter reports',
})
@swagger.ApiQuery({
name: 'from',
required: false,
description: 'Start date for filtering reports',
})
@swagger.ApiQuery({
name: 'to',
required: false,
description: 'End date for filtering reports',
})
@swagger.ApiQuery({
name: 'reportType',
required: false,
description: 'Type of reports to filter',
})
@swagger.ApiQuery({
name: 'riskLevels',
required: false,
description: 'Risk levels to filter by',
})
@swagger.ApiQuery({
name: 'statuses',
required: false,
description: 'Statuses to filter by',
})
@swagger.ApiQuery({
name: 'findings',
required: false,
description: 'Findings to filter by',
})
@swagger.ApiQuery({
name: 'isAlert',
required: false,
description: 'Filter by alert status',
})

Comment on lines +398 to 429
@swagger.ApiOperation({
summary: 'Create batch business reports',
description: 'Create multiple business reports from an uploaded file',
})
@swagger.ApiConsumes('multipart/form-data')
@swagger.ApiBody({
schema: {
type: 'object',
properties: {
file: {
type: 'string',
format: 'binary',
description: 'Excel/CSV file containing merchant data',
},
type: {
type: 'string',
description: 'Type of business reports to create',
},
workflowVersion: {
type: 'string',
description: 'Version of the workflow to use',
},
},
},
})
@swagger.ApiExcludeEndpoint()
@common.Post('/upload-batch')
@swagger.ApiForbiddenResponse({ type: errors.ForbiddenException })
@swagger.ApiForbiddenResponse({
description: 'Forbidden access',
type: errors.ForbiddenException,
})
@ApiConsumes('multipart/form-data')
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Resolve documentation visibility inconsistency and remove duplicate decorator.

Two issues found:

  1. The endpoint has detailed Swagger documentation but is marked with @ApiExcludeEndpoint().
  2. The @ApiConsumes('multipart/form-data') decorator is duplicated.
-  @swagger.ApiOperation({
-    summary: 'Create batch business reports',
-    description: 'Create multiple business reports from an uploaded file',
-  })
-  @swagger.ApiConsumes('multipart/form-data')
-  @swagger.ApiBody({
-    schema: {
-      type: 'object',
-      properties: {
-        file: {
-          type: 'string',
-          format: 'binary',
-          description: 'Excel/CSV file containing merchant data',
-        },
-        type: {
-          type: 'string',
-          description: 'Type of business reports to create',
-        },
-        workflowVersion: {
-          type: 'string',
-          description: 'Version of the workflow to use',
-        },
-      },
-    },
-  })
  @swagger.ApiExcludeEndpoint()
  @common.Post('/upload-batch')
  @swagger.ApiForbiddenResponse({
    description: 'Forbidden access',
    type: errors.ForbiddenException,
  })
- @ApiConsumes('multipart/form-data')
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@swagger.ApiOperation({
summary: 'Create batch business reports',
description: 'Create multiple business reports from an uploaded file',
})
@swagger.ApiConsumes('multipart/form-data')
@swagger.ApiBody({
schema: {
type: 'object',
properties: {
file: {
type: 'string',
format: 'binary',
description: 'Excel/CSV file containing merchant data',
},
type: {
type: 'string',
description: 'Type of business reports to create',
},
workflowVersion: {
type: 'string',
description: 'Version of the workflow to use',
},
},
},
})
@swagger.ApiExcludeEndpoint()
@common.Post('/upload-batch')
@swagger.ApiForbiddenResponse({ type: errors.ForbiddenException })
@swagger.ApiForbiddenResponse({
description: 'Forbidden access',
type: errors.ForbiddenException,
})
@ApiConsumes('multipart/form-data')
@swagger.ApiExcludeEndpoint()
@common.Post('/upload-batch')
@swagger.ApiForbiddenResponse({
description: 'Forbidden access',
type: errors.ForbiddenException,
})

Comment on lines +61 to 85
@swagger.ApiOperation({
summary: 'Get latest business report',
description:
'Retrieves the most recent business report for a given business ID and report type',
})
@swagger.ApiQuery({
name: 'businessId',
required: true,
description: 'ID of the business to get report for',
})
@swagger.ApiQuery({
name: 'type',
required: true,
description: 'Type of report to retrieve',
})
@common.Get('/latest')
@swagger.ApiOkResponse({ type: [String] })
@swagger.ApiForbiddenResponse({ type: errors.ForbiddenException })
@swagger.ApiOkResponse({
description: 'Latest report retrieved successfully',
type: [String],
})
@swagger.ApiForbiddenResponse({
description: 'Forbidden access',
type: errors.ForbiddenException,
})
@swagger.ApiExcludeEndpoint()
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Resolve documentation visibility inconsistency.

The endpoint has detailed Swagger documentation but is marked with @ApiExcludeEndpoint(), which prevents it from appearing in the Swagger UI. Either remove the @ApiExcludeEndpoint() decorator to make the documented endpoint visible, or remove the Swagger documentation if the endpoint should be hidden.

-  @swagger.ApiOperation({
-    summary: 'Get latest business report',
-    description:
-      'Retrieves the most recent business report for a given business ID and report type',
-  })
-  @swagger.ApiQuery({
-    name: 'businessId',
-    required: true,
-    description: 'ID of the business to get report for',
-  })
-  @swagger.ApiQuery({
-    name: 'type',
-    required: true,
-    description: 'Type of report to retrieve',
-  })
-  @swagger.ApiOkResponse({
-    description: 'Latest report retrieved successfully',
-    type: [String],
-  })
-  @swagger.ApiForbiddenResponse({
-    description: 'Forbidden access',
-    type: errors.ForbiddenException,
-  })
  @swagger.ApiExcludeEndpoint()
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@swagger.ApiOperation({
summary: 'Get latest business report',
description:
'Retrieves the most recent business report for a given business ID and report type',
})
@swagger.ApiQuery({
name: 'businessId',
required: true,
description: 'ID of the business to get report for',
})
@swagger.ApiQuery({
name: 'type',
required: true,
description: 'Type of report to retrieve',
})
@common.Get('/latest')
@swagger.ApiOkResponse({ type: [String] })
@swagger.ApiForbiddenResponse({ type: errors.ForbiddenException })
@swagger.ApiOkResponse({
description: 'Latest report retrieved successfully',
type: [String],
})
@swagger.ApiForbiddenResponse({
description: 'Forbidden access',
type: errors.ForbiddenException,
})
@swagger.ApiExcludeEndpoint()
@common.Get('/latest')
@swagger.ApiExcludeEndpoint()

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