Variables reutilization support

[natenho]

Some generated variables are useful to be repeatedly used inside the template body.

The feature could include "environment" or "global" variables, available to all templates and "scope" variables, available only to a given template.

[natenho]

This is partially supported. Starting in v1.2.0, there is the "Global" object, which can be used to persist global variables shared with all mocks.

It still lacks a way to naturally persist local script variables, so creating a variable inside a script like the example bellow is not supported so far:

<#
var myVariable = "my response";
#>
{
  "request": {
	"method": "GET",
	"route": "ping"
  },
  "response": {
	"status": "OK",
	"body": {
	  "response": "<#=myVariable #>"
	}
  }
}

[gomete]

Hi @natenho,

It would be nice to have this feature. Any idea about how to implement it? I could give it a try but I would appreciate some guidance.

[natenho]

@gomete We need to do a little research on how to design it and it would affect TempalteTransformer. The problem is that every script block (i.e. <# ... #>) is evaluated as independent scopes, hence not carrying any previous computed variables (even if they are in the same mock template).

The challenge is to implement a clean way to carry these variables along and only along a given mock scope.