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.

Sign up for GitHub

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

Jump to bottom

Inconsistent file naming strategy #3352

Open
calculuschild opened this issue Mar 14, 2024 · 1 comment
Open

Inconsistent file naming strategy #3352

calculuschild opened this issue Mar 14, 2024 · 1 comment
Labels
cleanup Cleaning up code for legibility, style, ease-of-use, etc. P3 - low priority Obscure tweak or fix for a single user tweak Small, non-breaking change

Comments

@calculuschild
Copy link
Member

@5e-Cleric has pointed out that we have a very inconsistent file/folder naming strategy

image

We got:

  • only one word
  • camelCase
  • underscore_naming
  • spaces
  • One word starting with caps

I would prefer camelCase, as it seems 90% of our file are already using that. Might be an easy project for someone to do.
@calculuschild calculuschild added cleanup Cleaning up code for legibility, style, ease-of-use, etc. P3 - low priority Obscure tweak or fix for a single user labels Mar 14, 2024
@5e-Cleric
Copy link
Member

5e-Cleric commented Mar 18, 2024 •
edited

With only three answers in two weeks, the form sent via gitter chat got the same answer, camelCase for both folder and files.

The only real problem will be updating all file paths, which should mostly be done automatically (VSC normally handles automatic path updating).

@5e-Cleric 5e-Cleric added the tweak Small, non-breaking change label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup Cleaning up code for legibility, style, ease-of-use, etc. P3 - low priority Obscure tweak or fix for a single user tweak Small, non-breaking change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@calculuschild @5e-Cleric