You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker (Specify the docker image that you're using and the command you used to start the container)
Other (Provide details of your environment)
Describe the bug
While configuring the input / output / settings of an activity / trigger added to a resource, I am able to assign a different type of data. There is no strict validation happening while configuring the input / settings / outputs.
With a strict type check in the configuration, we can avoid type coerce errors which occurs in run time while executing the resource.
To Reproduce
Steps to reproduce the behavior:
Go to a details page
Click on 'configure' (gear) icon from a tile's menu
Change a string type of input to some random number value
Save the configuration
Notice that no error is thrown to the user while editing or saving the configuration with a type difference.
Expected behavior
When user edits an attribute in the configuration, we should have a type check for primitive values.
Screenshots
Ex: In the above screenshot the counterName is of string type but the configuration does not complain when we provide a 435435 value. But we get an error when we run the binary.
The text was updated successfully, but these errors were encountered:
Environment
How are you running Flogo Web?
Describe the bug
While configuring the input / output / settings of an activity / trigger added to a resource, I am able to assign a different type of data. There is no strict validation happening while configuring the input / settings / outputs.
With a strict type check in the configuration, we can avoid type coerce errors which occurs in run time while executing the resource.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When user edits an attribute in the configuration, we should have a type check for primitive values.
Screenshots
Ex: In the above screenshot the
counterName
is of string type but the configuration does not complain when we provide a435435
value. But we get an error when we run the binary.The text was updated successfully, but these errors were encountered: