You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When viewing an API with many operations and definitions, each operation has the full list of all definitions, not just the ones that apply to the selected API operation. With a large API, this is odd.
For example, we have an operation with 4 different definitions in it's swagger, but we have 100s of types in the API operations overall, so there's 100s of definitions on the page.
To Reproduce
Steps to reproduce the behavior:
Import a Swagger API with many operations and definitions
Click on APIs
Select the API
Select an operation. Scrolling down you will see all definitions in the swagger spec, not just the ones in use in the operation
Expected behavior
Expect to only see the definitions that apply to the selected operation.
Portal environment
Managed
Release tag or commit SHA (if using self-hosted version)
unknown
Additional context
The operation's response model, with the 4 included definitions
A partial list of the definitions
The text was updated successfully, but these errors were encountered:
Describe the bug
When viewing an API with many operations and definitions, each operation has the full list of all definitions, not just the ones that apply to the selected API operation. With a large API, this is odd.
For example, we have an operation with 4 different definitions in it's swagger, but we have 100s of types in the API operations overall, so there's 100s of definitions on the page.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect to only see the definitions that apply to the selected operation.
Portal environment
Managed
Release tag or commit SHA (if using self-hosted version)
unknown
Additional context
The operation's response model, with the 4 included definitions
A partial list of the definitions
The text was updated successfully, but these errors were encountered: