support for variable system

[0hsn]

• http spec file: define variable and use in request #78
• Support for tags #250
• http spec file: define variable and use in output/expose #80
• http spec file: __import__ from external file #81
• http spec file: _invoke_ from scoped or imported variables #82
• support for new variable spec #128
• Read from OS Env for variables #192
• Read from .env file #193
• Advance variable management SQLite #335
• Filter function support for better data manipulation in variable templates <% a | first() %> #336
• Implement Jinja3 for variable value and filters #338
• Support .env.<platfrom> file loading from commandline #330

What

• define local variables
• define global variables
• expose scoped function data to local variable
• expose scoped function data to global variable
  • Specify expose / output variable on request

dump: :stdout '{.summary}\r\n{.headers}\r\n{.body}'
dump: :write(file:///home/user/file.txt) '{.summary}\r\n{.headers}\r\n{.body}'

• inject named parameters to specs
  • define argument
  • define option
• import variables to scope
• ability to read ENV vars on specs
• variable behavior modification with @annotation(...params) or [:annotation ...params]

---

Thoughts:

all variable gets name mangled on runtime
special keywords:
    _import_ ( array ) = list of files to be imported to current space. : can be used on variable specification format
        some/path/here/FileName => {FileName.VarName} : to import by absolute path, in-term of from where the commands get run
        ENV => {ENV.SHELL}  : import env variable
        SYSTEM => {SYSTEM.OS_VERSION} : import env variable
    _inject_ (string) = name of the variable, to be injected, not all component is injectable
    variable (object): list of all var in local scope : can be used on http, spec, flow etc
    new version type default:variable:...
Incremental update for variable features
    http: define variable and use in request
    http: define variable and use in description
    http: define variable and use in output/expose
        expose are 2 type
            calling from CLI
            calling from other spec
    ::import incrementally in spec files #issue

[0hsn]

Specify expose / output variable on request

What

---
request:
  ...
  expose:
    [tbd]

Why

it is needed for

• --expose= option
• output parsing
• general output formatting

[0hsn]

Value validation for variables

In describe section variables need sanity check

• type hint
• type check
• value validation