Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

{{'false' ? 'yes' : 'no'}} is interpreted as {{false ? 'yes' : 'no'}}

Open
#1,221 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
backend

Research direction

Start by reproducing the example with PARAM set to the string "false" and the conditional expression shown in the issue. Trace how Jinjava evaluates string values in boolean conditions; done means determining whether this is intended behavior or identifying a focused change and a regression test for preserving the string value.

Written by the indexing model from the issue text.

Description

Hello. I found that if a string has a boolean value, then it is interpreted as the boolean value it contains.
For example
PARAM = "false"
JINJA_EXPR = {{ PARAM ? PARAM : "" }}
After rendering JINJA_EXPR, the output is "" but I expect it to be "false" meaning the param is present and can be used.
Could you please explain how to remove this behavior? Or if the latter is not possible could you please tell me how to resolve the case I described?

Dominant language
Java
Stars
785
Forks
184
Avg merge
6d 22h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HubSpot/jinjava

All issues in HubSpot/jinjava

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.