This change contains various changes to the fnenv/native package. It adds the javascript function, which allows users to create tasks using javascript. In the backend it is evaluated using the already in place Otto javascript engine. The idea behind it is that it will allow users to trivial functions and to provide more self-describing workflows (for demos or examples).
This also adds a prototype of the repeat function, which is in anticipation of the dynamic/inline workflow support. Although not usable in the current state, it shows how the dynamic workflows can be used to implement interesting functions.
Finally, the types/typedvalues package as part of the dynamic workflows milestone, undergoes some refactoring as well as adding initial support for the workflow type.
This change contains various changes to the
fnenv/native
package. It adds thejavascript
function, which allows users to create tasks using javascript. In the backend it is evaluated using the already in place Otto javascript engine. The idea behind it is that it will allow users to trivial functions and to provide more self-describing workflows (for demos or examples).This also adds a prototype of the
repeat
function, which is in anticipation of the dynamic/inline workflow support. Although not usable in the current state, it shows how the dynamic workflows can be used to implement interesting functions.Finally, the
types/typedvalues
package as part of the dynamic workflows milestone, undergoes some refactoring as well as adding initial support for theworkflow
type.