juzhiyuan opened a new pull request, #3485: URL: https://github.com/apache/apisix-dashboard/pull/3485
**Why submit this pull request?** - [x] New feature provided ## Summary Add one keyword field to the Routes table, including the table within a Service. Match name, URI, host, configured plugin names, labels, status and description. ```text Browse routes → existing Admin API pagination First search → existing route list GET for the current scope Edit the keyword → filter the loaded routes and paginate in the browser Clear the keyword → return to the normal paginated list ``` Refs apache/apisix#14173 and #3205. ## Evidence - **Before** Official APISIX 3.19.0 shows 10 routes per page and places `billing-payment-retry` on page 201 of a 2,001-route fixture. - **After** In the same APISIX environment, entering `payment-retry` shows the target on page 1. The first search returned 2,001 routes in 616,540 JSON bytes. Subsequent keywords reused the list. - Build and lint passed. All 198 unit tests and 6 Playwright tests passed, covering server pagination, search across pages, clear and no-match behavior, Service scope and CRUD. ## Merge Danger **Door** Two-way. Revert the Dashboard change to remove the search field. **Blast radius** Routes. The first search reads all routes in the current scope through the existing Admin API, so response size grows with the route configurations. **Checklist** - [x] Explain the feature and its behavior - [x] Add corresponding test cases - [x] Document usage in the README - [x] Preserve compatibility with the existing Admin API -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
