Open sybernix opened 4 years ago
This happens due to the required parameter annotation at the connector level. If a parameter is defined as optional=false
it should have a non-empty value. Hence this needs to be fixed at the connector level, making the parameter optional and an empty string default value.
Or else what we can do is showing all the mandatory fields as of the above screenshot, but make them non-required fields. WDYT?
@niruhan @sajithshn @CharukaK
Is it possible to pass an empty string from the UI? I think that is how we are handling DBs without password when writing the Siddhi app password=""
Hmm if we allow empty string then we cannot verify mandatory fields neh..
I have three ideas.
if its mandatory and if its a password field we can have check box to allow empty values since technically that is possible. I do not think in other cases we need that coz if its mandatory we need to provide a value . WDYT ?
@dnwick @niruhan What about making the password field an optional and have an empty string as the default value?
@lasanthaS normally password is mandatory right ? so IMO we should not change it in the backend rather handle it in the client side
Description: We can have a user without password in databases. However, ETL wizard mandates that we provide a value for password
Affected Product Version: 1.1.0