Skip to content

[BUG] None is rendered as none, not None #715

@fornwall

Description

@fornwall

Describe the bug
When rendering none/None in jinja, fusion renders none, while core/jinja2 renders None.

Mostly an annoying thing when diffing the compilation result between core and fusion.

What version of dbt Fusion is this bug in? (find out by running dbt --version)
dbt-fusion 2.0.0-preview.9

Is this a discrepancy between the dbt Fusion Engine and dbt Core? Check one.

  • YES
  • NO

To Reproduce

  1. Open this workspace
  2. Follow the instructions in the README

Or follow the original instructions below:

Execute

dbt compile --quiet --inline "{{ None }} and {{ none }}"

Expected behavior
The string None and None should be rendered, as with dbt-core.

Actual behavior
The string none and none is rendered.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdiscrepancydiscrepancy between the dbt Fusion Engine and dbt Corehas-reproHas a reproducible example

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions