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

Inconsistent listing of APIs in Change API Provider feature #3241

Closed
tharikaGitHub opened this issue Oct 10, 2024 · 0 comments · Fixed by wso2/carbon-apimgt#12679
Closed

Comments

@tharikaGitHub
Copy link
Member

Description

When there are multiple documents and API Products available in the server, the Admin portal Change API Provider API listing table shows inconsistent results.

This is due to the behaviour of the content search api we are using to retrieve the APIs. Content search means we search for all content including APIs, API Products and Documents as well. The default limit for the rest api call is 10. If we obtain 10 resources out of which none are APIs, the apiList becomes empty. If this happens for the first set of results, the UI shows a message No Data to Display and hence it is not possible to navigate through to the next paginated content in the table.

Screenshot 2024-10-10 at 19 45 04

If we search using the lowercase naming of an API, search results will show up as it now searches for a specific content with a query.

The UI is only supposed to display APIs while all content including API Products and Documents are searched for resulting in the misleading behaviour with pagination.

Steps to Reproduce

  1. Login to API Publisher and create multiple APIs, API Products and Documents amounting to more than 10 API Products and Documents.
  2. Login to Admin portal and try accessing the Change API Provider page.
  3. You will see inconsistent pagination results.

Affected Component

APIM

Version

4.3.0, 4.4.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants