We could think about removing the glyphicon- prefix from the icon property as all icons are glyphicons anyway
We should use the isTruthy utility from the view-utils instead of using state => state in the Indicator component
I am not a fan of having two icons to indicate the connection status. To me this seems like a technical detail we could hide from the business user. My proposal would be to have only one icon. Something like "Status: " or "Status: ". The info what is broken can be included in the tooltip.
Sebastian Stamm
added a comment -
Should we have tests for the Icon widget?
We could think about removing the glyphicon- prefix from the icon property as all icons are glyphicons anyway
We should use the isTruthy utility from the view-utils instead of using state => state in the Indicator component
I am not a fan of having two icons to indicate the connection status. To me this seems like a technical detail we could hide from the business user. My proposal would be to have only one icon. Something like "Status: " or "Status: ". The info what is broken can be included in the tooltip.
Icon widgets doesn't have any logic really. It is just something that generates static html. So we could test that, but what is the point?
Yeah, that makes sense and with it some tests would make sense actually
Hm... We could do that, although this information is hidden from business user anyway, because that is displayed only during import (something configured and monitored by tech stuff I guess). Although it makes sense to have one icon anyway.
Mariusz
added a comment - - edited sebastian.stamm
Icon widgets doesn't have any logic really. It is just something that generates static html. So we could test that, but what is the point?
Yeah, that makes sense and with it some tests would make sense actually
Hm... We could do that, although this information is hidden from business user anyway, because that is displayed only during import (something configured and monitored by tech stuff I guess). Although it makes sense to have one icon anyway.
Regarding tests for the icon widget: It isn't really super critical. One thing we could test is, that it correctly sets the class-name on the element.
Sebastian Stamm
added a comment - Regarding tests for the icon widget: It isn't really super critical. One thing we could test is, that it correctly sets the class-name on the element.
I guess this indicator shows up during data import only, correct?
Michael Schoettes
added a comment - mariusz.sielski , according to the issue description the footer bar in optimize should contain something like
{
"connectedToEngine" : true ,
"connectedToElasticsearch" : true
}
I guess this indicator shows up during data import only, correct?
I am not a fan of having two icons to indicate the connection status. To me this seems like a technical detail we could hide from the business user. My proposal would be to have only one icon. Something like "Status:
" or "Status:
". The info what is broken can be included in the tooltip.