I think instead of introducing another new property, it's better to make *default **value * property optional. If there is no default value in the template, then that field becomes mandatory for the user.
On Tue, Oct 16, 2018 at 11:07 AM Niveathika Rajendran <[email protected]> wrote: > Hi All, > > As of the current implementation, we have assumed that the user input of > the templated field is optional, i.e, always a default value should be > provided in the template. > > However, in some cases, it is not possible to give default values such, > 1. Latitude, longitude field templated siddhi apps used for Geofencing > 2. App Id in twitter source > > IMO, we should have another property added to the template field such as > "isUserInputMandatory". In this case, we should validate that all > properties should have non-empty values(Default values is not applicable). > > *Workaround Tried:* > I tried to add a script to validate that the input is non-empty. However, > then the default values will be validated at the template loading thus the > template becomes broken. > > Your thoughts on the matter are much appreciated. > > Github Issue: https://github.com/wso2/carbon-analytics/issues/1465 > > Best Regards, > *Niveathika Rajendran,* > *Software Engineer.* > *Mobile : +94 077 903 7536* > > > > -- *Minudika Gammanpila* Software Engineer - WSO2 Email : [email protected] Mobile : +94715659887 Web : http://wso2.com <http://wso2.com> <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
