Blows chunks when defining a function above an array

[PS-davetemplin]

WORKS

JSLT

def remove_html(text)
  replace($text, "</?h3\\s?[^>]*>", "")

{
  "title" : remove_html(.html)
}

INPUT

{"html": "<h3>hello</h3>"}

DOES NOT WORK

JSLT

def remove_html(text)
  replace($text, "</?h3\\s?[^>]*>", "")

[for (.) {
  "title" : remove_html(.html)
}]

INPUT

[{"html": "<h3>hello</h3>"}]

BLOWS CHUNKS...

ERROR: com.schibsted.spt.data.jslt.JsltException: Parse error: Encountered " "for" "for "" at line 4, column 2.
Was expecting one of:
    "null" ...
    <INTEGER> ...
    <DECIMAL> ...
    <STRING> ...
    "[" ...
    ":" ...
    "{" ...
    "true" ...
    "false" ...
    "." ...
    "if" ...
    "(" ...
    <IDENT> ...
    <PIDENT> ...
    <VARIABLE> ...
     at <inline>:4:1

[larsga]

This is a syntax ambiguity in the language grammar. It's pretty confusing, so I think we need to do something about this.

JSLT thinks the [for(...) ...] is an array index on the output of the value inside the remove_html function.

If you do this

def remove_html(text)
  (replace($text, "</?h3\\s?[^>]*>", ""))

[for (.) {
  "title" : remove_html(.html)
}]

it will work.

[PS-davetemplin]

Thanks for the workaround!

[catull]

I make it a habit to have an "entry" method and implicit call at the end of a .jslt file, say

def remove_html (text)
  replace ($text, "</?h3\\s?[^>]*>", "")

def transform ()
  [for (.) {
    "title" : remove_html (.html)
  }]

transform () // implicit call

It has the advantage that it can be tested in the JSLT Playground [1].
Has worked and is a "pattern" for us.

We have noticed that if the main method is not called - and therefore parsed, you may see runtime errors that the method is not found.

Perhaps this is an old behaviour ...

[1] JSLT Playground

[PS-davetemplin]

That's cool!