-
Notifications
You must be signed in to change notification settings - Fork 176
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
Swagger APIView for PR 21841 is missing information #5376
Comments
@mikekistler Here is the fix version APIView of communicationEmail service https://apiviewstaging.azurewebsites.net/Assemblies/Review/cce8b46c14a947dd9a74d636b52f725a The first issue has been fixed. And the second issue will be fixed in this PR. #5386 |
The first issue is occurring in APIViews generated as recently as 4 days ago: https://apiview.dev/Assemblies/Review/3a169944515241f7b57e3fb70b9bb92d |
This issue happened on this PR. Azure/azure-rest-api-specs#22316 @praveenkuttappan . I have already updated the swagger-api-parser version in spec PR pipeline. And the generated APIView artifact file is correct. But the APIView website doesn't pick up the latest APIView file. |
I see the issue in APIView when a new revision is available. Swagger API review has collapsible section, and this is not correctly considered when calculating the diff. I will look into it to find a solution. |
The Swagger APIView for PR 21841 is missing several important bits of information on the REST API:
Operation-Id
header parameter for POST on /emails:send is not rendered.The text was updated successfully, but these errors were encountered: