Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2268
One example of separating widget with value types.
```
//
https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/tabledata/advanced-transformation-util.test.js#L19-L25
const MockParameter = {
'floatParam': { valueType: 'float', defaultValue: 10, description: '', },
'intParam': { valueType: 'int', defaultValue: 50, description: '', },
'jsonParam': { valueType: 'JSON', defaultValue: '', description: '',
widget: 'textarea', },
'stringParam1': { valueType: 'string', defaultValue: '', description: '',
},
'stringParam2': { valueType: 'string', defaultValue: '', description: '',
widget: 'input', },
'boolParam': { valueType: 'boolean', defaultValue: false, description:
'', widget: 'checkbox', },
'optionParam': { valueType: 'string', defaultValue: 'line', description:
'', widget: 'option', optionValues: [ 'line', 'smoothedLine', ], },
}
```
1. In case of password, value type will be decided by its definition. If
it's number, we can validate it as number. (string as well)
2. In case of combobox, type will be boolean.
3. We can parse values based on their type like
https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/tabledata/advanced-transformation-util.js#L85-#L117
4. I think it's not complicated. IMO, it's the part we should design
carefully since it's hard to change (backward compatibility)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
