10000 Expose more variables to Jinja templates · Issue #922 · fsfe/reuse-tool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Expose more variables to Jinja templates #922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BigBlueHat opened this issue Feb 26, 2024 · 3 comments
Closed

Expose more variables to Jinja templates #922

BigBlueHat opened this issue Feb 26, 2024 · 3 comments

Comments

@BigBlueHat
Copy link
Contributor

This would solve a host of issues around text formatting and whitespace and be useful next to #581.

@davidlehn
Copy link

An issue this might address is the copyright date range issue from #915. merge_copyright_lines in _util.py uses spaces in the date range formatting:

                year = f"{min(years)} - {max(years)}"

When used in a template, there is no flexibility if one wanted to use what seems to be the far more common spaceless "YYYY-YYYY" range form:

{% for copyright_line in copyright_lines %}
{{ copyright_line }}
{% endfor %}

I'm not sure if more vars is the right approach for this particular issue. It might make the templates too complex? May need something to control the logic in the function that does the formatting.

Copy link

Thank you for your time and contributions! Unfortunately, this issue has been inactive for quite a while which means we probably can't manage the time to deal with it. That's why we're marking it as stale. We want to keep things tidy and focus on active discussions, but we’re always happy to revisit if this is still relevant!

If you’d like to keep this open, please add a comment to let us know and remove the label stale. Otherwise, this issue will most likely be automatically closed soon.

@github-actions github-actions bot added the stale label Mar 22, 2025
Copy link

Since there hasn't been any recent activity after the last message, we're going to go ahead and close this issue. Feel free to reopen this and remove the labels stale and unresolved if it's urgent.

We truly appreciate your contributions and engagement!

Thank you and happy hacking!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0