oscal-compass/compliance-trestle

feat: add debug capability to trestle jinja support

Open

#1,960 opened on Oct 22, 2025

View on GitHub
 (8 comments) (0 reactions) (2 assignees)Python (103 forks)auto 404
event/slamexempt-from-stalehelp wantedmarkdown / Authorpython

Repository metrics

Stars
 (264 stars)
PR merge metrics
 (PR metrics pending)

Description

Issue description / feature objectives

Presently, when there is an issue with trestle author jinja there is no ability to debug. For example, issue #1953.

Proposed:

Include the following in trestle/core/commands/author/jinja.py:

def jinja_debug_filter(value):
    print(f"DEBUG: {value}")  # Print to console for debugging
    return value  # Return the original value to maintain template flow

Then, where ever jinja Environment is created, for example:

jinja_env = Environment(
            loader=FileSystemLoader(template_folder), extensions=extensions(), trim_blocks=True, autoescape=True
        )

Follow with this code:

jinja_env.filters['debug'] = jinja_debug_filter

This will enable templates do add debugging.

In template: {{"group.id:"~group.id|debug}}

In produced markdown: group.id:AC.2

Caveats / Assumptions

Commensurate test cases and documentation.

Completion Criteria

Contributor guide