Skip to content

JinjaProxy should use StrictUndefined #606

@sanderr

Description

@sanderr

JinjaProxy returns Jinja's Undefined when core raises an OptionalValueException or an UnsetException. From the Jinja docs I suspect StrictUndefined may be more appropriate, though there could be backwards compatibility concerns. This should be investigated (don't take the premise for granted, I haven't gone in depth).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    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