You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/09/20 02:44:00 UTC
[jira] [Assigned] (IGNITE-9339) Web console: form-field-size
improvements
[ https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kuznetsov reassigned IGNITE-9339:
----------------------------------------
Assignee: Alexander Kalinin (was: Dmitriy Shabalin)
> Web console: form-field-size improvements
> -----------------------------------------
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
> Reporter: Ilya Borisov
> Assignee: Alexander Kalinin
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact that {{form-field-size}} converts visible value when user changes scale. He suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now some form fields use different default scale (i.e. it's bytes vs megabytes). [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can figure out a better component API for cases like this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)