[
https://issues.apache.org/jira/browse/SOLR-17660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis updated SOLR-17660:
----------------------------------------
Description:
Many UI elements in the new designs of the Admin UI use a table-like or list
component with a filter on top and some actions left and right. This component
can be implemented in a way that can be reused, allowing a quicker
implementation of components that follow the same pattern.
h2. Task
Implement a reusable list component that is for now based on the needs of the
list shown in the logging section. Use the logging section as first
implementation for evaluation of the UI component's "interface".
h2. Acceptance Criteria
- The top bar (input field) has dynamic actions on the right
- The action on the left can optionally be added / displayed
- The input can be cleared with a clear button \(x)
- The clear button \(x) is hidden when the input is empty
- The child elements are passed by the parent (are dynamic)
- The list is horizontally scrollable if a child is longer than the available
width
- The list is vertically scrollable if the amount of children exceed the
available height
For the logs in the logging section it is sufficient to keep it simple and only
display the values of the field. Another ticket will add additional
functionality and support (like coloring and wrapping).
h2. Additional Information
You do not have to add support for a header / column names. That comes with
additional requirements like sorting, that should be avoided for now. Do not
aim for perfection, as not all requirements are clarified right now.
If there is a ready-to-use component from a compose UI libary that can be used
and simply styled, consider using that instead.
was:
Many UI elements in the new designs of the Admin UI use a table-like or list
component with a filter on top and some actions left and right. This component
can be implemented in a way that can be reused, allowing a quicker
implementation of components that follow the same pattern.
h2. Task
Implement a reusable list component that is for now based on the needs of the
list shown in the logging section. Use the logging section as first
implementation for evaluation of the UI component's "interface".
h2. Acceptance Criteria
- The top bar (input field) has dynamic actions on the right
- The action on the left can optionally be added / displayed
- The input can be cleared with a clear button (x)
- The clear button (x) is hidden when the input is empty
- The child elements are passed by the parent (are dynamic)
- The list is horizontally scrollable if a child is longer than the available
width
- The list is vertically scrollable if the amount of children exceed the
available height
For the logs in the logging section it is sufficient to keep it simple and only
display the values of the field. Another ticket will add additional
functionality and support (like coloring and wrapping).
h2. Additional Information
You do not have to add support for a header / column names. That comes with
additional requirements like sorting, that should be avoided for now. Do not
aim for perfection, as not all requirements are clarified right now.
If there is a ready-to-use component from a compose UI libary that can be used
and simply styled, consider using that instead.
> Implement basic list component in Admin UI
> ------------------------------------------
>
> Key: SOLR-17660
> URL: https://issues.apache.org/jira/browse/SOLR-17660
> Project: Solr
> Issue Type: New Feature
> Components: Admin UI
> Reporter: Christos Malliaridis
> Priority: Major
> Labels: new-ui, ui
>
> Many UI elements in the new designs of the Admin UI use a table-like or list
> component with a filter on top and some actions left and right. This
> component can be implemented in a way that can be reused, allowing a quicker
> implementation of components that follow the same pattern.
> h2. Task
> Implement a reusable list component that is for now based on the needs of the
> list shown in the logging section. Use the logging section as first
> implementation for evaluation of the UI component's "interface".
> h2. Acceptance Criteria
> - The top bar (input field) has dynamic actions on the right
> - The action on the left can optionally be added / displayed
> - The input can be cleared with a clear button \(x)
> - The clear button \(x) is hidden when the input is empty
> - The child elements are passed by the parent (are dynamic)
> - The list is horizontally scrollable if a child is longer than the available
> width
> - The list is vertically scrollable if the amount of children exceed the
> available height
> For the logs in the logging section it is sufficient to keep it simple and
> only display the values of the field. Another ticket will add additional
> functionality and support (like coloring and wrapping).
> h2. Additional Information
> You do not have to add support for a header / column names. That comes with
> additional requirements like sorting, that should be avoided for now. Do not
> aim for perfection, as not all requirements are clarified right now.
> If there is a ready-to-use component from a compose UI libary that can be
> used and simply styled, consider using that instead.
--
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
