Skip to content
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

Auto-update copyright year #247

Open
mfisher87 opened this issue Jan 12, 2024 · 4 comments
Open

Auto-update copyright year #247

mfisher87 opened this issue Jan 12, 2024 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers impact/ui Impacts the the user interface

Comments

@mfisher87
Copy link
Member

This is super low-priority, but it'd be nice to have :)

@mfisher87 mfisher87 added enhancement New feature or request good first issue Good for newcomers impact/ui Impacts the the user interface labels Jan 12, 2024
@Sherwin-14
Copy link
Contributor

Hey, do you have some specific suggestions regarding this.

@mfisher87
Copy link
Member Author

Hey Sherwin, good to hear from you :) I think one good way is to continue using the Jinja global mechanism we're using to pass in the documentation URLs, etc., and use that to pass current_year=dt.date.today().year. What do you think?

Another option would be to pass in the whole datetime module so then templates can use it to do arbitrary date stuff.

I don't have strong feelings either way, and it would be easy to change later if we want.

@Sherwin-14
Copy link
Contributor

Sherwin-14 commented Jan 16, 2024

Hey, I too had thought about the solutions that you suggested and i was thinking maybe we should make a single file where we can incorporate all the changes like this one , i think that would help a lot in identifying all the changes.

@mfisher87
Copy link
Member Author

maybe we should make a single file where we can incorporate all the changes like this one , i think that would help a lot in identifying all the changes.

Not sure I get it 100%. Do you mean create a single Jinja template for footer; or create a single Python file for the code which handles configuring the globals?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers impact/ui Impacts the the user interface
Projects
Status: No status
Development

No branches or pull requests

2 participants