Repository navigation
Proposal: Develop a uniform naming convention #41
Description
Activity
As well as doc strings.
I would +1 to an overall style guideline in addition to the current CONTRIBUTING tutorial. However, I also understand that things are still moving fast at this early stage and perhaps a loose standard is preferred.
As well as doc strings.
I would +1 to an overall style guideline in addition to the current CONTRIBUTING tutorial. However, I also understand that things are still moving fast at this early stage and perhaps a loose standard is preferred.
Maybe you're right, we may have to wait a while to unify these things. This way we can maximize our productivity.
If it is a simple restriction identifier style (such as
snake_caseorCamelCase), it should not have any impact. The current overall code style issnake_case.- locked and limited conversation to collaborators
on Mar 28, 2024
The existing Pull requests are slightly different from the existing code in the core repository in terms of function names and test names. Is it necessary to develop a unified standard to manage?