Variable Name with Hyphen Misinterpreted in Conditional Statements

[sai-prasad-1]

I am encountering an issue when trying to use a variable with a hyphen (-) in its name within a conditional statement in a markdown file. The variable loads and renders correctly using {{site.data.scam-banner}}, but when I attempt to use it within an if block or similar control structures, it throws an error. It appears that the hyphen in the variable name is being interpreted as a minus sign.

{% if site.data.messages.scam-banner %}
{{ site.data.messages.scam-banner }}
{% else %}
Error: 'messages.farewell' variable not found
{% endif %}

[error] stack trace is suppressed; run last Compile / run for the full output
[error] (Compile / run) liqp.exceptions.LiquidException: parser error "mismatched input '-' expecting {TagEnd, '.', NEq, '==', '>=', '>', '<=', '<', '[', '?', 'contains', 'and', 'or'}" on line 7, index 29

is this an bug or does liqp not support this type of variables.

[sai-prasad-1]

@bkiers

[msangel]

@sai-prasad-1 Hello!
Could you please provide sample code how you define this variable?

[msangel]

According to Ruby syntax the is not valid part of identifier, so not wonder the error there as it looks like expression:
site.data.messages.scam -(minus) banner.

Are these variables works in original liquid templator?

[sai-prasad-1]

I am using this package in Scala, and the variables are loaded from a YAML file as a HashMap and passed to the LIQP parser. I am able to access these variables using {{ }} in any template but not within any tags or blocks.

// Convert the dataMap to Java Map for LIQP usage
    val convertedDataMap = new util.HashMap[String, Any]()
    dataMap.foreach { case (k, v) => convertedDataMap.put(k, v) }
    innerMap.putAll(convertedDataMap)
    siteVariables.put("site", innerMap)
    val md = liqpParser.parse(rawMarkdown).render(siteVariables)
    ```
This is how the values are passed.

if you need anything else please let me know

[msangel]

Glad to inform that right now the library behave exactly as liquid native implementation.
Its allow these as variable for assigning and printing BUT fails to use in if conditions.
So not seeing error here as behavior ported properly.

[msangel]

That's was liquid... looks like liquid required the second argument even the documentation stayed it is not.... Weird...


So the error above because no second argument of condition.

anycase, site.data.messages.scam-banner is an expression. Expression that shouldn't be in if tag

[msangel]

Ok. That expectation about second argument in example above came after failure correctly parse the if expression in original liquid/jekyll. as the minus in not allowed there either, so it thinks there more input.

SO the original library thinks variable with minus is not allowed in if conditions

[sai-prasad-1]

so in short what is the way to go around and solve or overcome the issue like i am using the JEKYLL flavour of liqp and the same thing is working over there in jekyl, and also as you mentioned the block is not considering the value as null/nill so is this something that could be fixed over time

[msangel]

@sai-prasad-1 I see no other workaround then not use variables with minus in their names. Don't believe original Liquid/Jekyll will allow them either as it is invalid ruby identifier as well.

[msangel]

I tried to workaround this with assign/capture, but their syntax also not allows such names.