[
https://issues.apache.org/jira/browse/SOLR-17896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis updated SOLR-17896:
----------------------------------------
Description:
Many of our sections come with tabs that divide top-level sections into smaller
sections. This can be implemented as a reusable component that can be extended
by the top-level componets and use a generic to dynamically load the tabs.
h2. Task
Implement a tab navigation component (and/or migrate existing components) that
is reusable by other components.
h2. Acceptance Criteria
- The navigation component integration avoids duplication of code and logic
- The navigation component is using well-defined (preferrably enums or sealed
classes / objects) values for the menu items
- The implementation **may** output navigation events
- The implementation **may** prevent conditionally navigation actions
- That is, when the user wants to navigate to different tab for example, but
there is an unsaved state currently present that will be lost on navigation
- The styles from the Figma designs (see section's header, most of them have
tabs, e.g. for
[configsets|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=227-7661&t=yxFihPpG3r7FXACm-1])
are appled.
h2. Additional Information
The navigation component may be added to the following sections:
- Metrics
- Cluster
- Security (note here the different navigation tabs based on current security
configuration)
- Configsets
- Collections
- Logging
See the current [figma
designs|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=87-12957&t=Nn13TbrCARmj2IrX-1]
for details about each section's tabs.
was:
Many of our sections come with tabs that divide top-level sections into smaller
sections. This can be implemented as a reusable component that can be extended
by the top-level componets and use a generic to dynamically load the tabs.
h2. Task
Implement a navigation component (and/or migrate existing components) that is
reusable by other components.
h2. Acceptance Criteria
- The navigation component integration avoids duplication of code and logic
- The navigation component is using well-defined (preferrably enums or sealed
classes / objects) values for the menu items
- The implementation **may** output navigation events
- The implementation **may** prevent conditionally navigation actions
- That is, when the user wants to navigate to different tab for example, but
there is an unsaved state currently present that will be lost on navigation
h2. Additional Information
The navigation component may be added to the following sections:
- Metrics
- Cluster
- Security (note here the different navigation tabs based on current security
configuration)
- Configsets
- Collections
- Logging
See the current [figma
designs|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=87-12957&t=Nn13TbrCARmj2IrX-1]
for details about each section's tabs.
> Implement a Reusable Tab Navigation Component
> ---------------------------------------------
>
> Key: SOLR-17896
> URL: https://issues.apache.org/jira/browse/SOLR-17896
> Project: Solr
> Issue Type: Sub-task
> Components: Admin UI
> Reporter: Christos Malliaridis
> Assignee: Christos Malliaridis
> Priority: Major
> Labels: new-ui, ui
>
> Many of our sections come with tabs that divide top-level sections into
> smaller sections. This can be implemented as a reusable component that can be
> extended by the top-level componets and use a generic to dynamically load the
> tabs.
> h2. Task
> Implement a tab navigation component (and/or migrate existing components)
> that is reusable by other components.
> h2. Acceptance Criteria
> - The navigation component integration avoids duplication of code and logic
> - The navigation component is using well-defined (preferrably enums or sealed
> classes / objects) values for the menu items
> - The implementation **may** output navigation events
> - The implementation **may** prevent conditionally navigation actions
> - That is, when the user wants to navigate to different tab for example,
> but there is an unsaved state currently present that will be lost on
> navigation
> - The styles from the Figma designs (see section's header, most of them have
> tabs, e.g. for
> [configsets|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=227-7661&t=yxFihPpG3r7FXACm-1])
> are appled.
> h2. Additional Information
> The navigation component may be added to the following sections:
> - Metrics
> - Cluster
> - Security (note here the different navigation tabs based on current security
> configuration)
> - Configsets
> - Collections
> - Logging
> See the current [figma
> designs|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=87-12957&t=Nn13TbrCARmj2IrX-1]
> for details about each section's tabs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
