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

Standardize naming for files + urls #4330

Open
wes-otf opened this issue Jan 9, 2025 · 3 comments
Open

Standardize naming for files + urls #4330

wes-otf opened this issue Jan 9, 2025 · 3 comments
Assignees

Comments

@wes-otf
Copy link
Contributor

wes-otf commented Jan 9, 2025

A kinda simple one but it might make sense to "standardize" how we name things a bit. A few examples:

Partial names between projects & applications are snake vs kebab case, and applications specify partial in the name:

path("partial/lead/", partial_project_lead, name="project_lead"),
path("partial/title/", partial_project_title, name="project_title"),

name="partial-get-lead",

the same applies to filenames, there's a mix of snake & kebab in templates


Is there a difference between naming folders include or includes?:
ie. /apply/activity/templates/activity/include/ vs /apply/templates/forms/includes/

@wes-otf
Copy link
Contributor Author

wes-otf commented Jan 9, 2025

definitely not a priority, just was noticing it a bit as I was poking around today and wanted to document

@frjo
Copy link
Member

frjo commented Jan 10, 2025

I find it a lot easier to find and remember things that are named consistently so +1.

@theskumar theskumar self-assigned this Jan 15, 2025
@theskumar
Copy link
Member

I'll try clean this up.

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

3 participants