[
https://issues.apache.org/jira/browse/SOLR-17849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019243#comment-18019243
]
Christos Malliaridis edited comment on SOLR-17849 at 10/24/25 1:37 PM:
-----------------------------------------------------------------------
-This ticket is solved if a reusable tab navigation component is implemented
(avoids duplication).-
The above comment is partly incorrect, as this ticket does not address the
navigation (only), but instead focuses on the UI elements in the header.
was (Author: JIRAUSER305622):
This ticket is solved if a reusable tab navigation component is implemented
(avoids duplication).
> Implement Index & Query section header
> --------------------------------------
>
> Key: SOLR-17849
> URL: https://issues.apache.org/jira/browse/SOLR-17849
> Project: Solr
> Issue Type: Sub-task
> Components: Admin UI
> Reporter: Christos Malliaridis
> Priority: Major
> Labels: new-ui, newdev, ui
>
> In the Index & Query section the header contains two dropdown options, one is
> for selecting the collection and one the request handler.
> h2. Task
> Implement the two drop-downs that allow the user to select a collection and,
> based on the collection, get a list of available request handlers. See the
> [Index &
> Query|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=137-12066&t=3d0o3InCzstyUJ40-1]
> designs for the details.
> h2. Acceptance Criteria
> - The available collections are listed
> - The user can select a collection
> - The available request handlers are loaded based on the collection that is
> currently selected
> - The user can select a request handler when a collection is selected
> - The currently selected collection and request handler are part of the state
> - When selecting a request handler a placeholder text is shown
> - When there are no collections available both dropdowns are disabled
> - When there are no collections available a message is displayed that
> notifies the user that no collections are available
> - When a collection has no request handlers, a message that notifies the user
> is displayed
> - The dropdowns are disabled during loading phases
> - when collections are loaded, both drop-downs are disabled
> - when collection is selected and request handlers are being loaded, only
> request handler drodown is disabled
> - The dropdown of the reques thandlers shows the endpoint (name) and the
> request handler (class) are displayed
> - Note that the class may be longer than the available space the dropdown
> has, so take that into account when chooses sizes, shortening or wrapping
> texts
> h2. Additional Information
> You should not implement the actual form of a request handler, this is part
> of a separate task.
> Some API endpoints may not be available in the OpenAPI spec, so you have to
> find the places in the documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
