docs(api): Add swagger docs of API key controller

[rajdip-b]

User description

Fixes #86

---

Type

Documentation, Enhancement

---

Description

• Added comprehensive Swagger documentation to ApiKeyController, including operation summaries, parameter descriptions, and response schemas.
• Documented DTO properties in CreateApiKey with Swagger for better API documentation.
• Removed unused mock user data file to clean up the codebase.

---

Changes walkthrough

	Relevant files
Documentation	api-key.controller.ts Enhance API Key Controller with Swagger Documentation        apps/api/src/api-key/controller/api-key.controller.ts Added Swagger decorators for API documentation in ApiKeyController. Introduced HTTP status code and response schema documentation for each endpoint. Enhanced API security documentation with @ApiBearerAuth and @ApiSecurity. +149/-1  create.api-key.ts Document CreateApiKey DTO Properties with Swagger                apps/api/src/api-key/dto/create.api-key/create.api-key.ts Added @ApiProperty decorators to document properties of CreateApiKey DTO. +24/-0
Miscellaneous	users.ts Remove Unused Mock User Data                                                          apps/api/src/common/mock-data/users.ts Removed mock user data file. +0/-40

---

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-free]

PR Description updated to latest commit (c6e8f48)

[codiumai-pr-agent-free]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the changes are mostly related to adding annotations for Swagger documentation. These changes are straightforward and primarily involve adding metadata to existing endpoints and DTOs. The removal of the mock data file is also a simple change.
🧪 Relevant tests	No
🔍 Possible issues	Possible Oversight: The default value for the page query parameter in getApiKeysOfUser method has been changed from 1 to 0. This might affect pagination logic if the underlying service expects page numbering to start from 1.
🔒 Security concerns	No

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

[codiumai-pr-agent-free]

PR Code Suggestions

Category	Suggestions
Maintainability	Use a shared constant for common properties in API key schemas to improve maintainability. Consider using a shared constant for the apiKeySchemaWithValue and apiKeySchema objects to avoid duplication of the schema structure. This will make the code more maintainable and reduce the risk of discrepancies between the schemas. apps/api/src/api-key/controller/api-key.controller.ts [32-55] +const baseProperties = { + id: { type: 'string' }, + name: { type: 'string' }, + expiresAt: { type: 'string' }, + authorities: { type: 'array', items: { type: 'string' } }, + createdAt: { type: 'string' }, + updatedAt: { type: 'string' } +}; const apiKeySchemaWithValue = { type: 'object', properties: { - id: { type: 'string' }, - name: { type: 'string' }, + ...baseProperties, value: { type: 'string' }, - expiresAt: { type: 'string' }, - authorities: { type: 'array', items: { type: 'string' } }, - createdAt: { type: 'string' }, - updatedAt: { type: 'string' } } } const apiKeySchema = { type: 'object', - properties: { - id: { type: 'string' }, - name: { type: 'string' }, - expiresAt: { type: 'string' }, - authorities: { type: 'array', items: { type: 'string' } }, - createdAt: { type: 'string' }, - updatedAt: { type: 'string' } - } + properties: baseProperties }
	Group Swagger decorators to improve readability and maintainability. To improve the readability and maintainability of the Swagger documentation decorators, consider grouping related decorators into a separate file or function. This approach can help in reusing common response patterns and keeping the controller code clean. apps/api/src/api-key/controller/api-key.controller.ts [64-74] -@ApiOperation({ - summary: 'Create API key', - description: 'This endpoint creates a new API key' -}) -@ApiCreatedResponse({ - schema: apiKeySchemaWithValue, - description: 'API key created successfully' -}) -@ApiForbiddenResponse(invalidAuthenticationResponse) +// Example of a decorator function +function ApiKeyCreationDocs() { + return applyDecorators( + ApiOperation({ + summary: 'Create API key', + description: 'This endpoint creates a new API key' + }), + ApiCreatedResponse({ + schema: apiKeySchemaWithValue, + description: 'API key created successfully' + }), + ApiForbiddenResponse(invalidAuthenticationResponse) + ); +} +// Usage in the controller +@ApiKeyCreationDocs()
Enhancement	Specify the schema property in @ApiParam to accurately document parameter types. For the @ApiParam decorator in the updateApiKey and deleteApiKey methods, consider specifying the schema property to enforce the type of the id parameter. This ensures that the Swagger documentation accurately reflects the expected parameter type. apps/api/src/api-key/controller/api-key.controller.ts [85-89] @ApiParam({ name: 'id', description: 'API key ID', required: true, - type: String + schema: { type: 'string' } })
Best practice	Use an enum for the expiresAfter property to enhance type safety and clarity. For the expiresAfter property in CreateApiKey class, consider using an enum for the allowed values instead of a union type. This will make the code more type-safe and the API documentation clearer by explicitly listing the allowed values. apps/api/src/api-key/dto/create.api-key/create.api-key.ts [26] -expiresAfter?: '24' | '168' | '720' | '8760' | 'never' = 'never' +enum ExpiresAfter { + TwentyFour = '24', + OneWeek = '168', + OneMonth = '720', + OneYear = '8760', + Never = 'never' +} +expiresAfter?: ExpiresAfter = ExpiresAfter.Never
	Implement a global exception filter for consistent error handling. To ensure consistent error handling and response formatting across the API, consider implementing a global exception filter that automatically handles common exceptions and formats them according to your API's response structure. This can reduce redundancy and improve maintainability. apps/api/src/api-key/controller/api-key.controller.ts [74] -@ApiForbiddenResponse(invalidAuthenticationResponse) +// Example of a global exception filter +@Catch(HttpException) +export class HttpExceptionFilter implements ExceptionFilter { + catch(exception: HttpException, host: ArgumentsHost) { + const ctx = host.switchToHttp(); + const response = ctx.getResponse<Response>(); + const status = exception.getStatus(); + const exceptionResponse = exception.getResponse(); + // Format and send the custom response + response + .status(status) + .json({ + statusCode: status, + message: exceptionResponse.message, + error: exceptionResponse.error, + }); + } +}

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

Enabling\disabling automation When you first install the app, the default mode for the improve tool is: pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] meaning the improve tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically.

Utilizing extra instructions Extra instructions are very important for the improve tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

A note on code suggestions quality While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the custom suggestions 💎 tool With large PRs, best quality will be obtained by using 'improve --extended' mode.

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the improve usage page for a more comprehensive guide on using this tool.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.80%. Comparing base (7bb3d21) to head (d9625f1).
Report is 28 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop     #167       +/-   ##
============================================
+ Coverage    62.20%   94.80%   +32.59%     
============================================
  Files           76       91       +15     
  Lines         1503     2001      +498     
  Branches       260      394      +134     
============================================
+ Hits           935     1897      +962     
+ Misses         568      104      -464     

Flag	Coverage Δ
api-e2e-tests	94.80% <100.00%> (+32.59%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rajdip-b]

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀