Implemented templates resolution for functions

[vemonet]

templates are when the user provides constant strings + reference variables to a function parameter, e.g. This person is: {FirstName} {LastName}

It was not resolving before (only constant and reference were implemented)

All tests are passing

[ThibaultGerrier]

Looks good!

This won't work with getting multiple values from the template:
e.g.

{ 
  "mult": ["foo", "bar"]
}

template: "{mult.*}" -> "foo,bar" instead of ["foo", "bar"]
or
template: "val: {mult.*}" -> "vals: foo,bar" instead of ["val: foo", "val: bar"]
or
template: "{mult.*}-{mult.*}" -> "foo,bar-foo-bar" instead of ["foo-foo", "foo-bar", "bar-foo", "bar-bar"] (doing all permutations is how templates work with the Java RML implementation)

If we'd want to support multiple values we could reuse calculateTemplate from

RocketRML/src/input-parser/parser.js

Line 409 in ca8b578

const calculateTemplate = (Parser, index, template, prefixes, termType, options) => {

. It would need a bit of refactoring though. (also looking at the code, termtype probably does not work with functions, but that's another issue..)

But since this is such a niche usecase and I'm not sure if it is supposed to work like that with functions, I'd be ok with this single string behavior.

If you could just add a var/let/const to 760f56e#diff-c739baa938dd5fea06c035a19eb7900313b820973dd508f0a8a7a644795b7cbaR32

[vemonet]

Indeed using calculateTemplate would make sense I wish I noticed it earlier! I fixed the missing const in the current implementation

[ThibaultGerrier]

Great thanks!
Published with v1.11.1