You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No. Upon revising the codebase, I first noticed some naming inconsistencies in the shfmt.nix file in comparison to others. This became more apparent when I compared it to other files like ruff.nix and prettier.nix. The inconsistencies involve the use of different naming conventions such as camelCase, snake_case, and kebab-case for module options. While this might seem like a minor issue, it could potentially lead to confusion or errors in the future.
Describe the solution you'd like
There should be a standard naming convention adopted for module options, especially for newer contributions. This standardization will help maintain consistency across the codebase and make it easier for developers to understand and contribute.
Describe alternatives you've considered
N/A
Additional context
There would be a significant amount of module renaming involved, so I'm curious how we would approach this process. How can we implement these changes efficiently and ensure a smooth transition without disrupting the current functionality?
Looking forward to thoughts and suggestions.
Greetings.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
No. Upon revising the codebase, I first noticed some naming inconsistencies in the
shfmt.nix
file in comparison to others. This became more apparent when I compared it to other files likeruff.nix
andprettier.nix
. The inconsistencies involve the use of different naming conventions such as camelCase, snake_case, and kebab-case for module options. While this might seem like a minor issue, it could potentially lead to confusion or errors in the future.Describe the solution you'd like
There should be a standard naming convention adopted for module options, especially for newer contributions. This standardization will help maintain consistency across the codebase and make it easier for developers to understand and contribute.
Describe alternatives you've considered
N/A
Additional context
There would be a significant amount of module renaming involved, so I'm curious how we would approach this process. How can we implement these changes efficiently and ensure a smooth transition without disrupting the current functionality?
Looking forward to thoughts and suggestions.
Greetings.
The text was updated successfully, but these errors were encountered: