Development

Testing

To run tests issue the following command in the root of the project:

go test -p 1 ./...

The -p 1 is needed to prevent tests from being run in parallel. To re-run the tests first run the following:

go clean -testcache

To skip the integration tests use the -short flag:

go test -p 1 -short ./...

Javascript Execution Activity

The jsexec activity evaluates a javascript script along with provided parameters and returns the result in the outputs.

The available service settings are as follows:

Name	Type	Description
script	string	The javascript code to evaluate

The available input for the request are as follows:

Name	Type	Description
parameters	JSON object	Key/value pairs representing parameters to evaluate within the context of the script

The available response outputs are as follows:

Name	Type	Description
error	bool	true if there is an error
errorMessage	string	The error message
result	JSON object	The result object from the javascript code

Microgateway Usage

A sample service definition is:

{
  "name": "JSCalc",
  "description": "Make calls to a JS calculator",
  "ref": "github.com/project-flogo/jsexec",
  "settings": {
    "script": "result.total = parameters.num * 2;"
  }
}

An example step that invokes the above JSCalc service using parameters is:

{
  "if": "$.PetStorePets.outputs.result.status == 'available'",
  "service": "JSCalc",
  "input": {
    "parameters.num": "=$.PetStorePets.outputs.result.available"
  }
}

Utilizing the response values can be seen in a response handler:

{
  "if": "$.PetStorePets.outputs.result.status == 'available'",
  "error": false,
  "output": {
    "code": 200,
    "data": {
      "body.pet": "=$.PetStorePets.outputs.result",
      "body.inventory": "=$.PetStoreInventory.outputs.result",
      "body.availableTimesTwo": "=$.JSCalc.outputs.result.total"
    }
  }
}