[
https://issues.apache.org/jira/browse/IGNITE-9680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-9680:
-
Description:
Create a component that output status:
1. It should accept a list of possible statuses as an argument, each item
should specify label to display, model value, color (red, green or regular) and
whether to show an inline spinner or not.
2. It should also accept status value as an argument.
3. Given that same the status might be displayed in various places, provide a
way to omit repeating lengthy statuses list argument. Maybe a component factory
that binds statuses to a new component?
4. The new component should be based on either _ignite-status_ component or
supersede it.
Use the new component in:
1. Connected clusters dialog.
was:
Create a component that output status:
1. It should accept a list of possible statuses as an argument, each item
should specify label to display, model value, color (red, green or regular) and
whether to show an inline spinner or not.
2. It should also accept status value as an argument.
3. Given that same the status might be displayed in various places, provide a
way to omit repeating lengthy statuses list argument. Maybe a component factory
that binds statuses to a new component?
Use the new component in:
1. Connected clusters dialog.
Remove the _ignite-status_ component.
> Web console: add component for status output
>
>
> Key: IGNITE-9680
> URL: https://issues.apache.org/jira/browse/IGNITE-9680
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
>
> Create a component that output status:
> 1. It should accept a list of possible statuses as an argument, each item
> should specify label to display, model value, color (red, green or regular)
> and whether to show an inline spinner or not.
> 2. It should also accept status value as an argument.
> 3. Given that same the status might be displayed in various places, provide a
> way to omit repeating lengthy statuses list argument. Maybe a component
> factory that binds statuses to a new component?
> 4. The new component should be based on either _ignite-status_ component or
> supersede it.
> Use the new component in:
> 1. Connected clusters dialog.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
