[
https://issues.apache.org/jira/browse/SOLR-17849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132601#comment-18132601
]
Nick Shanin commented on SOLR-17849:
------------------------------------
[~sandbergja] You said on 2025-10-23 that you would like to work on this
ticket. Are you still planning to? I do not want to duplicate work you have
started.
I have an implementation on a
[branch|https://github.com/nick-boss-tech/solr/tree/solr-17849-index-query-screen],
and the
[diff|https://github.com/apache/solr/compare/main...nick-boss-tech:solr-17849-index-query-screen]
is the Index and Query header and screen: {{IndexQueryHeader.kt}} and
{{IndexQueryContent.kt}} under
{{ui/shared/src/commonMain/kotlin/org/apache/solr/ui/views/indexquery/}}, a
data layer and state holder under {{components/indexquery/}}, and
{{RequestHandlerOption.kt}} in the domain package, with wiring in the
configsets components and strings. Tests: {{IndexQueryHeaderTest}},
{{IndexQueryContentTest}}, {{IndexQueryStateHolderTest}}. Spotless and those
tests pass at the gated head. The branch also carries the SearchHandler form
view, which is SOLR-17850's component.
If you are not working on it, [~malliaridis], is this the right scope for the
ticket, and would you review it if I open the branch as a PR?
🤖 _AI text above_ 🤖 _(reviewed by Nick Shanin)_
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
