Skip to content

Behaviour Change - Boolean True escaping to empty string #405

@gtrbunny

Description

@gtrbunny

Version: Appears to be related to the many commits ~ September/3, I have not yet located the exact commit. Happy to investigate further if it would be helpful.

Bug Description

Boolean true appears to be evaluated to empty string, prior to ~ September 3 it would be evaluated to 1. Unsure if this is expected behaviour, but this change has introduced subtle bugs in existing templates.

Steps To Reproduce

{do $value = true}
<input value="{$value}">
<input value="{(string)$value}">

Output:

<input name="name" value="">
<input name="name" value="1">

Expected Behaviour

Prior to ~ 3/Sep/2025, this would output:

<input name="name" value="1">
<input name="name" value="1">

Possible Solution

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions