[ https://issues.apache.org/jira/browse/SOLR-17847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christos Malliaridis updated SOLR-17847: ---------------------------------------- Description: In the Configsets we have multiple sub-sections the user can navigate to. These subections have to be accessible, so a basic navigation is needed here. h2. Task Implement a basic navigation where a basic "wrapper" component of the "Configsets" section handles the navigation between each section. You should implement a navigation that reflects the sub-sections from [the designs|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=14-3249&t=3d0o3InCzstyUJ40-1]. h2. Acceptance Criteria - The user can select and switch between the sub-sections - The content (child slot) of the screen is updated based on the navigation - you can use a placeholder component for each section's content that simply renders a text of the current section - The selected sub-section is highlighted - The navigation state is part of the wrapper - A dropdown with the available confisets is available - We may extend this in the future to allow the user to filter configsets by typing in (not relevant now) - The currently selected configset is part of the wrapper component h2. Additional Information The configset selection is part of the wrapper component and can be added to it. The actions next to it are however child-specific, so based on the current section the actions may be different. This can be handled by using two "child slots", one for the actions and one for the main content of the sub-section (content below). For simplicity, you can ignore in this task the actions and only provide a UI slot for the children (sub-sections). You may use the name ConfigsetsComponent and follow the typical naming conventions for component interfaces, implenetations etc. See existing components as an example. was: In the Configsets we have multiple sub-sections the user can navigate to. These subections have to be accessible, so a basic navigation is needed here. h2. Task Implement a basic navigation where a basic "wrapper" component of the "Configsets" section handles the navigation between each section. h2. Acceptance Criteria - The user can select and switch between the sub-sections - The content (child slot) of the screen is updated based on the navigation - you can use a placeholder component for each section's content that simply renders a text of the current section - The selected sub-section is highlighted - The navigation state is part of the wrapper - A dropdown with the available confisets is available - We may extend this in the future to allow the user to filter configsets by typing in (not relevant now) - The currently selected configset is part of the wrapper component h2. Additional Information The configset selection is part of the wrapper component and can be added to it. The actions next to it are however child-specific, so based on the current section the actions may be different. This can be handled by using two "child slots", one for the actions and one for the main content of the sub-section (content below). For simplicity, you can ignore in this task the actions and only provide a UI slot for the children (sub-sections). You may use the name ConfigsetsComponent and follow the typical naming conventions for component interfaces, implenetations etc. See existing components as an example. > Introduce Navigation to Configsets > ---------------------------------- > > Key: SOLR-17847 > URL: https://issues.apache.org/jira/browse/SOLR-17847 > Project: Solr > Issue Type: Sub-task > Components: Admin UI > Reporter: Christos Malliaridis > Priority: Major > Labels: new-ui, newdev, ui > > In the Configsets we have multiple sub-sections the user can navigate to. > These subections have to be accessible, so a basic navigation is needed here. > h2. Task > Implement a basic navigation where a basic "wrapper" component of the > "Configsets" section handles the navigation between each section. You should > implement a navigation that reflects the sub-sections from [the > designs|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=14-3249&t=3d0o3InCzstyUJ40-1]. > h2. Acceptance Criteria > - The user can select and switch between the sub-sections > - The content (child slot) of the screen is updated based on the navigation > - you can use a placeholder component for each section's content that > simply renders a text of the current section > - The selected sub-section is highlighted > - The navigation state is part of the wrapper > - A dropdown with the available confisets is available > - We may extend this in the future to allow the user to filter configsets > by typing in (not relevant now) > - The currently selected configset is part of the wrapper component > h2. Additional Information > The configset selection is part of the wrapper component and can be added to > it. The actions next to it are however child-specific, so based on the > current section the actions may be different. This can be handled by using > two "child slots", one for the actions and one for the main content of the > sub-section (content below). > For simplicity, you can ignore in this task the actions and only provide a UI > slot for the children (sub-sections). > You may use the name ConfigsetsComponent and follow the typical naming > conventions for component interfaces, implenetations etc. See existing > components as an example. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org