Every bug report should have precise description and reproduction steps; console traces or source code references are appreciated.
For assistance requests, contact Azure support or submit a post on Stack Overflow. We don't provide support through GitHub Issues. Feature requests can be raised on the Azure Feedback Forum.
Bug description
The api-details widget performs a check if the currently selected API has a version set associated. It then queries all available version sets for version sets for matches. The second query returns a pageable dataset and the KnockoutJS is only fetching the first page.
Reproduction steps
Add a high number of APIs with version sets (approximately 150)
Select an API with a version set that is returned by the first query to apis?$filter=isCurrent%20eq%20true&api-version=2021-04-01-preview
Note the version selector is displayed
Select an API with a version set that is not returned by the first query to apis?$filter=isCurrent%20eq%20true&api-version=2021-04-01-preview
Note the version selector is not displayed
Expected behavior
I expect the KnockoutJS code to traverse all pages of the API result to make the determination on whether or not to display the version selector.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
API Management service name
Environment
Operating system: N/A
Browser: N/A
Additional context
Code to determine if API has version sets:
Code to determine if the version selector should be displayed (bug here):
Hello @BenAtOB , thanks for reaching out and for the detailed explanation! 🙌
This issue was fixed (for managed portals) and will be shipped with the next release (ETA end of month).
Every bug report should have precise description and reproduction steps; console traces or source code references are appreciated.
For assistance requests, contact Azure support or submit a post on Stack Overflow. We don't provide support through GitHub Issues. Feature requests can be raised on the Azure Feedback Forum.
Bug description
The api-details widget performs a check if the currently selected API has a version set associated. It then queries all available version sets for version sets for matches. The second query returns a pageable dataset and the KnockoutJS is only fetching the first page.
Reproduction steps
Expected behavior
I expect the KnockoutJS code to traverse all pages of the API result to make the determination on whether or not to display the version selector.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
API Management service name
Environment
Additional context
Code to determine if API has version sets:![image](https://github.com/Azure/api-management-developer-portal/assets/144714590/0f58cedd-d8f0-44df-bcb7-210fea04dc83)
Code to determine if the version selector should be displayed (bug here):![image](https://github.com/Azure/api-management-developer-portal/assets/144714590/9cae1dc0-4b42-4cb9-805d-2888bba10ad7)