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

fix(webapi): Set correct swagger return type for transmission list #1590

Merged

Conversation

oskogstad
Copy link
Collaborator

Description

Related Issue(s)

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

  • Documentation is updated (either in docs-directory, Altinnpedia or a separate linked PR in altinn-studio-docs., if applicable)

@oskogstad oskogstad requested a review from a team as a code owner December 11, 2024 11:13
Copy link
Contributor

coderabbitai bot commented Dec 11, 2024

📝 Walkthrough

Walkthrough

The pull request introduces significant updates to the OpenAPI specification for the Dialogporten API, primarily in the swagger.verified.json file. Key changes include restructuring schema definitions to reflect array formats, adding new properties and detailed descriptions to existing schemas, standardizing error response schemas, refining endpoint descriptions, and maintaining security definitions. Additionally, the SearchDialogTransmissionEndpoint class was modified to change the return type from a single object to a list of objects, ensuring consistency with the updated schema definitions.

Changes

File Change Summary
docs/schema/V1/swagger.verified.json - Updated schema V1ServiceOwnerDialogTransmissionsQueriesSearch_Transmission to include array structure.
- Enhanced V1ServiceOwnerDialogsCommandsCreate_DialogCommand with new properties and descriptions.
- Standardized error response schemas including ProblemDetails.
- Updated V1ServiceOwnerDialogsQueriesGet_Dialog with additional properties and descriptions.
src/Digdir.Domain.Dialogporten.WebApi/Endpoints/V1/ServiceOwner/DialogTransmissions/Search/SearchDialogTransmissionEndpoint.cs - Changed return type in Description method from ProducesOneOf<TransmissionDto> to ProducesOneOf<List<TransmissionDto>>.

Possibly related PRs

Suggested reviewers

  • MagnusSandgren

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e624fef and 1969c77.

📒 Files selected for processing (2)
  • docs/schema/V1/swagger.verified.json (1 hunks)
  • src/Digdir.Domain.Dialogporten.WebApi/Endpoints/V1/ServiceOwner/DialogTransmissions/Search/SearchDialogTransmissionEndpoint.cs (1 hunks)
🔇 Additional comments (5)
src/Digdir.Domain.Dialogporten.WebApi/Endpoints/V1/ServiceOwner/DialogTransmissions/Search/SearchDialogTransmissionEndpoint.cs (2)

25-28: LGTM! Documentation now correctly reflects the implementation.

The change properly aligns the OpenAPI/Swagger documentation with the actual return type of the endpoint, which returns a list of transmissions.


25-28: Verify OpenAPI specification alignment.

Let's ensure the OpenAPI specification is consistently updated across all references to this endpoint.

docs/schema/V1/swagger.verified.json (3)

6750-6753: LGTM! Return type correctly updated to array.

The return type for transmission list has been properly updated to return an array of transmissions, which aligns with the actual API behavior.


6750-6753: Schema definitions are well-structured and documented.

The transmission schemas are properly defined with:

  • Clear descriptions for each field
  • Proper validation rules
  • Consistent naming conventions
  • Comprehensive documentation

6750-6753: Verify consistent return type usage across endpoints.

Let's verify that the array return type is consistently used across all transmission-related endpoints.

✅ Verification successful

Return type is consistently defined across transmission endpoints

Both endpoints (V1EndUserDialogTransmissionsSearch_SearchDialogTransmission and V1ServiceOwnerDialogTransmissionsSearch_SearchDialogTransmission) consistently define their response schemas as arrays:

  • EndUser endpoint returns array of V1EndUserDialogTransmissionsQueriesSearch_Transmission
  • ServiceOwner endpoint returns array of V1ServiceOwnerDialogTransmissionsQueriesSearch_Transmission
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistency in transmission list return types
# Expected: All transmission list endpoints should return array types

# Search for transmission list endpoints and their return types
rg -A 5 "V1.*DialogTransmissionsSearch_SearchDialogTransmission" 

Length of output: 938


Script:

#!/bin/bash
# Let's check the response schema for both endpoints to verify array type consistency

# First, let's get the full context for V1EndUserDialogTransmissionsSearch_SearchDialogTransmission
rg -B 5 -A 15 "V1EndUserDialogTransmissionsSearch_SearchDialogTransmission.*responses" docs/schema/V1/swagger.verified.json

# Then, let's get the full context for V1ServiceOwnerDialogTransmissionsSearch_SearchDialogTransmission
rg -B 5 -A 15 "V1ServiceOwnerDialogTransmissionsSearch_SearchDialogTransmission.*responses" docs/schema/V1/swagger.verified.json

Length of output: 256


Script:

#!/bin/bash
# Let's try a different approach to get the response schemas
# Search for the entire endpoint definitions including their responses

# For EndUser endpoint
rg -A 50 '"V1EndUserDialogTransmissionsSearch_SearchDialogTransmission"' docs/schema/V1/swagger.verified.json

# For ServiceOwner endpoint
rg -A 50 '"V1ServiceOwnerDialogTransmissionsSearch_SearchDialogTransmission"' docs/schema/V1/swagger.verified.json

Length of output: 3725


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. (Experiment)
  • @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.

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.

@oskogstad oskogstad merged commit 6e88e0c into main Dec 11, 2024
25 checks passed
@oskogstad oskogstad deleted the fix/set-correct-return-type-for-so-transmission-list branch December 11, 2024 12:44
arealmaas pushed a commit that referenced this pull request Dec 12, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.41.2](v1.41.1...v1.41.2)
(2024-12-12)


### Bug Fixes

* **webapi:** Set correct swagger return type for transmission list
([#1590](#1590))
([6e88e0c](6e88e0c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

2 participants